Methods and devices for wireless communications

ABSTRACT

A central trajectory controller including a cell interface configured to establish signaling connections with one or more backhaul moving cells and to establish signaling connections with one or more outer moving cells, an input data repository configured to obtain input data related to a radio environment of the one or more outer moving cells and the one or more backhaul moving cells, and a trajectory processor configured to determine, based on the input data, first coarse trajectories for the one or more backhaul moving cells and second coarse trajectories for the one or more outer moving cells, the cell interface further configured to send the first coarse trajectories to the one or more backhaul moving cells and to send the second coarse trajectories to the one or more outer moving cells.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. application Ser. No. 16/830,423, filed onMar. 26, 2020, which claims priority to PCT ApplicationPCT/US2018/039890, filed on Jun. 28, 2018, which claims priority to U.S.Patent Application Ser. No. 62/612,327, filed Dec. 30, 2017, and toIndian Patent Application Serial No. 201741047375, filed Dec. 30, 2017,all of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

Various aspects relate generally to methods and devices for wirelesscommunications.

BACKGROUND

Developments in radio communication networks have led to various newtypes of network architectures. Some of these network architecturesrelate to heterogenous networks, where both larger macro cells and smallcells are deployed in a coverage area. The macro cells may serve largecoverage areas while the small cells serve more limited spaces. Othernetwork architectures including moving cells, such as cells that can usemobility to improve coverage to their served terminal devices.Additional networks may use vehicular communication devices, wherevehicles can be equipped with connectivity functionality to wirelesslycommunicate with each other and the underlying network.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference characters generally refer to the sameparts throughout the different views. The drawings are not necessarilyto scale, emphasis instead generally being placed upon illustrating theprinciples of the disclosure. In the following description, variousaspects of the disclosure are described with reference to the followingdrawings, in which:

FIG. 1 shows an exemplary radio communication network according to someaspects;

FIG. 2 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIG. 3 shows an exemplary internal configuration of a network accessnode according to some aspects;

FIG. 4 shows an exemplary radio communication network with a corenetwork according to some aspects;

FIG. 5 shows an exemplary vehicular communication device according tosome aspects;

FIG. 6 shows an exemplary internal configuration of vehicularcommunication device according to some aspects;

FIG. 7 shows an exemplary network scenario with backhaul and outermoving cells according to some aspects;

FIG. 8 shows an exemplary internal configuration of an outer moving cellaccording to some aspects;

FIG. 9 shows an exemplary internal configuration of a backhaul movingcell according to some aspects;

FIG. 10 shows an exemplary internal configuration of a centraltrajectory controller according to some aspects;

FIG. 11 shows an exemplary trajectory control procedure for backhaul andouter moving cells according to some aspects;

FIG. 12 shows an exemplary radio map according to some aspects;

FIG. 13 shows an exemplary network scenario with backhaul moving cellsaccording to some aspects;

FIG. 14 shows an exemplary trajectory control procedure for backhaulmoving cells according to some aspects;

FIG. 15 shows an exemplary method for a central trajectory controlleraccording to some aspects;

FIG. 16 shows an exemplary method for an outer moving cell according tosome aspects;

FIG. 17 shows an exemplary method for a backhaul moving cell accordingto some aspects;

FIG. 18 shows an exemplary method for a central trajectory controlleraccording to some aspects;

FIG. 19 shows an exemplary method for a backhaul moving cell accordingto some aspects;

FIG. 20 shows an exemplary indoor coverage area according to someaspects;

FIG. 21 shows a diagram for mobile access nodes and an anchor accesspoint according to some aspects;

FIG. 22 shows an exemplary internal configuration of a mobile accessnode according to some aspects;

FIG. 23 shows an exemplary internal configuration of an anchor accesspoint according to some aspects;

FIG. 24 shows an exemplary procedure for mobile access nodes and ananchor access point according to some aspects;

FIG. 25 shows an exemplary method for identify usage patterns accordingto some aspects;

FIG. 26 shows an exemplary scenario of adjusting a trajectory of amobile access node according to some aspects;

FIG. 27 shows an exemplary scenario for adjusting a trajectory of amobile access node based on a trajectory departure according to someaspects;

FIG. 28 shows an exemplary method for a mobile access node according tosome aspects;

FIG. 29 shows an exemplary method for a mobile access node according tosome aspects;

FIG. 30 shows an exemplary method for a mobile access node according tosome aspects;

FIG. 31 shows an exemplary method for an anchor access point accordingto some aspects;

FIG. 32 shows an exemplary scenario of an indoor coverage area accordingto some aspects;

FIG. 33 shows an exemplary internal configuration of a mobile accessnode according to some aspects;

FIG. 34 shows an exemplary internal configuration of a centraltrajectory controller according to some aspects;

FIG. 35 shows an exemplary procedure for determining trajectories formobile access nodes according to some aspects;

FIG. 36 shows an exemplary procedure for determining trajectories formobile access nodes according to some aspects;

FIG. 37 shows an exemplary network scenario for beamsteering accordingto some aspects;

FIG. 38 shows an exemplary procedure for determining trajectories ofmobile access nodes based on capacity according to some aspects;

FIG. 39 shows an exemplary method for a central trajectory controlleraccording to some aspects;

FIG. 40 shows an exemplary method for a mobile access node according tosome aspects;

FIG. 41 shows an exemplary method for a mobile access node according tosome aspects;

FIG. 42 shows an exemplary method for a central trajectory controlleraccording to some aspects;

FIG. 43 shows an exemplary diagram of a virtual network according tosome aspects;

FIG. 44 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIG. 45 shows an exemplary procedure for forming and using a virtualnetwork according to some aspects;

FIG. 46 shows an exemplary procedure for using a virtual network with avirtual master terminal device according to some aspects;

FIG. 47 shows an exemplary diagram of various VEFs for a virtual networkaccording to some aspects;

FIGS. 48 and 49 show examples of distributing VEFs in a virtual networkaccording to some aspects;

FIG. 50 shows an exemplary procedure for executing VEFs according tosome aspects;

FIG. 51 shows an exemplary method of allocating VEFs according to someaspects;

FIG. 52 shows an exemplary procedure for forming and using a virtualcell according to some aspects;

FIG. 53 shows an exemplary network diagram of a virtual cell accordingto some aspects;

FIG. 54 shows an example illustrating allocation and execution ofvirtual cell VEFs at terminal devices according to some aspects;

FIG. 55 shows an exemplary diagram of virtual cell VEF allocation andexecution according to some aspects;

FIG. 56 shows an exemplary procedure for managing members of a virtualcell according to some aspects;

FIG. 57 shows an exemplary network scenario of handover for a virtualcell according to some aspects;

FIG. 58 shows an exemplary method of operating a terminal deviceaccording to some aspects;

FIG. 59 shows an exemplary method of operating a terminal deviceaccording to some aspects;

FIG. 60 shows an exemplary method of operating a terminal deviceaccording to some aspects;

FIG. 61 shows an exemplary network scenario for a virtual cell accordingto some aspects;

FIG. 62 shows an exemplary internal configuration of a terminal devicefor a virtual cell according to some aspects;

FIG. 63 shows an exemplary procedure for creating a virtual cellaccording to some aspects;

FIG. 64 shows an exemplary diagram of a virtual cell with differentregions according to some aspects;

FIG. 65 shows an exemplary diagram of a virtual cell according to someaspects;

FIG. 66 shows an example where a virtual cell is divided into multiplesubareas according to some aspects;

FIGS. 67 and 68 show examples of virtual cell VEF allocation accordingto some aspects;

FIG. 69 shows an exemplary division of a virtual cell coverage areaaccording to some aspects;

FIGS. 70 and 71 show examples of virtual cell VEF allocation accordingto some aspects;

FIG. 72 shows an example of mobility for served terminal devices ofvirtual cells according to some aspects;

FIG. 73 shows an exemplary virtual cell VEF allocation with a mobilitylayer according to some aspects;

FIGS. 74-79 show exemplary methods of operating communication devicesaccording to some aspects;

FIG. 80 shows an exemplary diagram of dynamic local server processingoffload according to some aspects;

FIG. 81 shows an exemplary internal configuration of a network accessnode according to some aspects;

FIG. 82 shows an exemplary internal configuration of a local serveraccording to some aspects;

FIG. 83 shows an exemplary internal configuration of a user plane serveraccording to some aspects;

FIG. 84 shows an exemplary internal configuration of a cloud serveraccording to some aspects;

FIG. 85 shows an exemplary procedure for dynamic local server processingoffload according to some aspects;

FIG. 86 shows an exemplary procedure for dynamic local server processingoffload according to some aspects;

FIG. 87 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIG. 88 shows an exemplary procedure for dynamic local server processingoffload according to some aspects;

FIG. 89 shows an exemplary procedure for dynamic local server processingoffload according to some aspects;

FIGS. 90-93 show exemplary methods for performing processing functionsat a local server according to some aspects;

FIG. 94 shows an exemplary method for filtering and routing dataaccording to some aspects;

FIGS. 95 and 96 show exemplary methods for execution at a cloud serveraccording to some aspects FIG. 97 shows an exemplary networkconfiguration for a cell association function according to some aspects;

FIG. 98 shows an exemplary internal configuration of cell associationcontroller according to some aspects;

FIGS. 99 and 100 show exemplary procedures for a cell associationfunction according to some aspects;

FIGS. 101-103 show various exemplary network scenarios for cellassociation according to some aspects;

FIGS. 104-106 show exemplary selections of MEC servers according to someaspects;

FIG. 107 shows an exemplary internal configuration of a bias controlserver according to some aspects;

FIG. 108 shows an exemplary procedure for determining bias valuesaccording to some aspects;

FIGS. 109 and 110 show exemplary procedures for controlling cellassociation according to some aspects;

FIG. 111 shows an exemplary method of determining bias values accordingto some aspects;

FIG. 112 shows an exemplary radio communication network employing CSMAaccording to some aspects;

FIG. 113 shows an exemplary method according to which terminal devicesmay communicate following a CSMA scheme according to some aspects;

FIG. 114 shows an exemplary radio communication network relating to fullduplex communication according to various aspects of the presentdisclosure;

FIG. 115 shows a further exemplary radio communication network relatingto full duplex communication according to various aspects of the presentdisclosure;

FIG. 116 shows a further exemplary radio communication network relatingto full duplex communication according to various aspects of the presentdisclosure;

FIG. 117 shows an exemplary internal configuration of a communicationdevice in accordance with various aspects of the present disclosure;

FIG. 118 shows an exemplary method, which a communication device mayexecute using the internal configuration of FIG. 117 in accordance withsome aspects;

FIGS. 119A and 119B show exemplary timing diagrams in accordance withcertain aspects; and

FIGS. 120A and 120B, illustrate exemplary frequency resources that mayin certain aspects be used for broadcasting scheduling messages.

FIG. 121 shows an exemplary method for a communication device accordingto some aspects;

FIGS. 122-125 show exemplary illustrations implementing full duplex (FD)methods in some aspects.

FIG. 126 shows an exemplary device configuration for low power Δ betweentransmitter and receiver for FD in some aspects.

FIG. 127 shows an exemplary device configuration for high power Δbetween transmitter and receiver for FD in some aspects.

FIG. 128 shows an exemplary configuration of a terminal device in someaspects.

FIG. 129 shows an exemplary Message Sequence Chart (MSC) for Cluster IDcreation/allocation in some aspects.

FIG. 130 shows an exemplary flowchart describing a method forcommunicating between a first device and a second device in someaspects.

FIG. 131 shows an exemplary flowchart describing a method for wirelesscommunications in some aspects.

FIG. 132 illustrates problems identified in V2X communications in someaspects.

FIG. 133 shows an exemplary network configuration and frequency, time,and power graph in some aspects FIG. 134 shows an exemplary internalconfiguration for a low-complexity broadcasting repeater (LBR) in someaspects.

FIG. 135 shows an exemplary flowchart describing a method for wirelesscommunications in some aspects,

FIG. 136 shows an exemplary small cell deployment problem scenario insome aspects.

FIG. 137 shows exemplary small cell configurations in some aspects.

FIG. 138 shows an exemplary scenario in which a node may be configuredas a relay to execute transformation/translation services betweendifferent RATs in some aspects.

FIG. 139 shows an exemplary internal configuration for a terminal devicein some aspects.

FIG. 140 shows an exemplary internal configuration for a deviceconfigured to process different RAT signals in some aspects.

FIG. 141 shows an exemplary flowchart describing a method for deployinga small cell communication arrangement in some aspects.

FIG. 142 shows an exemplary flowchart describing a method fortranslating a first radio access technology (RAT) signal into a secondRAT signal in some aspects.

FIG. 143 shows an exemplary RRC state transition chart in some aspects.

FIG. 144 shows an exemplary message sequence chart (MSC) illustrating aterminal device RX calibration in some aspects.

FIG. 145 shows an exemplary message sequence chart (MSC) illustrating aterminal device TX calibration in some aspects.

FIG. 146-147 show exemplary diagrams for an software reconfigurationbased replacement of defective source components in some aspects.

FIG. 148 shows an exemplary diagram illustrating a hardware replacementof defective source components in a terminal device in some aspects.

FIG. 149 shows an exemplary diagram for a hardware reconfiguration basedreplacement of defective source components in some aspects.

FIG. 150 shows an exemplary flowchart describing a method forcalibrating a communication device in some aspects.

FIG. 151 shows an exemplary flowchart describing replacing a componentof a communication device in some aspects.

FIG. 152 shows an exemplary flowchart describing a method for selectinga RAT link for transmitting a message in some aspects.

FIG. 153 shows an exemplary MSC with a corresponding small cell networkin some aspects.

FIG. 154-155 show exemplary diagrams for small cell reconfiguration insome aspects.

FIG. 156 shows an exemplary small cell network with a plurality ofspecialized small cells in some aspects.

FIG. 157 shows an exemplary MSC for the signaling of a small cellnetwork in some aspects.

FIG. 158 shows an exemplary flowchart describing a method for a networkaccess node to interact with users in some aspects.

FIG. 159 shows an exemplary flowchart describing management of a networkaccess node arrangement including a master network access node and oneor more dedicated network access nodes in some aspects.

FIG. 160 shows a diagram highlighting differences between reconfiguringa single terminal device compared to reconfiguring a small cell in someaspects.

FIG. 161 shows an exemplary small cell architecture according to someaspects.

FIG. 162 shows an exemplary overall system architecture for providingupdates to the small cell in some aspects.

FIG. 163 shows an exemplary small cell priority determiner in someaspects.

FIG. 164 shows an exemplary MSC describing a signaling process for asmall cell network in some aspects.

FIG. 165 shows an exemplary flowchart describing a method forconfiguring a network access node in some aspects.

FIG. 166 shows an exemplary an exemplary V2X network environment in someaspects.

FIG. 167 shows an exemplary diagram describing an exemplary hierarchicalsetup in some aspects.

FIG. 168A shows an exemplary internal configuration for a hierarchydeterminer of a terminal device in some aspects.

FIG. 168B shows an exemplary an exemplary MSC describing a method foridentifying capabilities of one or more small cells for determining asmall cell hierarchy in some aspects.

FIG. 168C shows an exemplary diagram describing a process for meetinglatency requirements in some aspects.

FIG. 168D shows an exemplary small cell network configuration in someaspects.

FIG. 169 shows an exemplary flowchart describing a method for creating ahierarchy of nodes for use in wireless communications in some aspects.

FIG. 170 shows an example of a transmitting and receiving streams ofuser plane data according to some aspects;

FIG. 171 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIG. 172 shows an exemplary network scenario of dynamic compressionselection with multiple network access nodes according to some aspects;

FIGS. 173 and 174 show exemplary procedures for dynamic compressionselection in uplink and downlink according to some aspects;

FIG. 175 shows an exemplary network scenario of dynamic compressionselection with one network access node according to some aspects;

FIGS. 176 and 177 show exemplary procedures for dynamic compressionselection in uplink and downlink according to some aspects;

FIG. 178 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIGS. 179-181 show exemplary methods of transferring a data stream atacommunication device according to some aspects;

FIG. 182 shows an example of a network communication scenario accordingto some aspects;

FIG. 183 shows an exemplary internal configuration of a network accessnode according to some aspects;

FIG. 184 shows an exemplary procedure for a modulation scheme selectionfunction according to some aspects;

FIG. 185 shows an exemplary procedure for a modulation scheme selectionfunction with additional control variables according to some aspects;

FIG. 186 shows an exemplary procedure for a modulation scheme selectionfunction with spectrum offload according to some aspects;

FIG. 187 shows an exemplary network scenario for a modulation schemeselection function with multiple terminal devices according to someaspects;

FIG. 188 shows an exemplary procedure for a modulation scheme selectionfunction with multiple terminal devices according to some aspects;

FIG. 189 shows an exemplary procedure for a modulation scheme selectionfunction at a terminal device according to some aspects;

FIG. 190 shows an exemplary procedure for operating a network accessnode according to some aspects;

FIG. 191 shows an exemplary procedure for operating a terminal deviceaccording to some aspects;

FIG. 192 shows an exemplary procedure for operating a network accessnode according to some aspects;

FIG. 193 shows an exemplary internal configuration of a radiocommunication arrangement, and an antenna system according to someaspects.

FIG. 194 shows an exemplary network scenario in accordance with someaspects.

FIG. 195 shows an exemplary flow diagram for a device under testaccording to some aspects.

FIG. 196 shows an exemplary flow diagram for a device under testaccording to some aspects.

FIG. 197 shows an exemplary process for performing a conformance test ofa device under test according to some aspects.

FIG. 198 shows an exemplary process for performing an OTA update processaccording to some aspects.

FIG. 199 is an exemplary message sequence chart according to someaspects.

FIG. 200 shows an exemplary method for communicating over a radiocommunication network in accordance with some aspects.

FIG. 201 shows an exemplary method for communicating over a radiocommunication network in accordance with some aspects.

FIG. 202 shows an exemplary decision chart for an in-field diagnosticprocess according to some aspects.

FIG. 203 shows an exemplary evaluation of an in-field diagnostic processin accordance with some aspects.

FIG. 204 shows an exemplary internal configuration of a radiocommunication arrangement, and an antenna system according to someaspects.

FIG. 205 shows an exemplary network scenario in accordance with someaspects.

FIG. 206 shows an exemplary logical architecture of a radiocommunication arrangement in accordance with some aspects.

FIG. 207 shows an exemplary logical architecture of a radiocommunication arrangement in accordance with some aspects.

FIG. 208 is an exemplary message sequence chart in accordance with someaspects.

FIG. 209 is an exemplary message sequence chart in accordance with someaspects.

FIG. 210 is an exemplary message sequence chart in accordance with someaspects.

FIG. 211 shows an exemplary method for communicating over a radiocommunication network in accordance with some aspects.

FIG. 212 shows an exemplary method for communicating over a radiocommunication network in accordance with some aspects.

FIG. 213 shows an exemplary unmanned aerial vehicle according to someaspects;

FIG. 214 shows an exemplary unmanned aerial vehicle with a flightstructure according to some aspects;

FIG. 215 shows an exemplary change in a target zone and target locationaccording to some aspects;

FIG. 216 shows an exemplary change in a target zone and target locationaccording to some aspects;

FIG. 217 shows an exemplary flight path according to some aspects;

FIG. 218 shows an exemplary flight path according to some aspects;

FIG. 219 shows an exemplary flight path according to some aspects;

FIG. 220 shows an exemplary method for flying on a flight path accordingto some aspects;

FIG. 221 shows an exemplary method for flying on a flight path accordingto some aspects;

FIG. 222 shows an exemplary flight formation according to some aspects;

FIG. 223 shows an exemplary flight formation according to some aspects;

FIG. 224 shows an exemplary flight formation according to some aspects;

FIG. 225 shows an exemplary method for arranging a flight formationaccording to some aspects;

FIG. 226 shows an exemplary relay for a network access node according tosome aspects;

FIG. 227 shows an exemplary relay for a network access node according tosome aspects;

FIG. 228 shows an exemplary method for controlling a relay for a networkaccess node according to some aspects;

FIG. 229 shows an exemplary two-dimensional cell network according tosome aspects;

FIG. 230 shows an exemplary three-dimensional cell network according tosome aspects;

FIG. 231 shows an exemplary unmanned aerial vehicle according to someaspects;

FIG. 232 shows an exemplary flight path for charging an unmanned aerialvehicle according to some aspects;

FIG. 233 shows an exemplary method for charging an unmanned aerialvehicle according to some aspects;

FIG. 234 shows an exemplary structure for charging an unmanned aerialvehicle according to some aspects;

FIG. 235 shows an exemplary method for charging an unmanned aerialvehicle according to some aspects;

FIG. 236 shows an exemplary arrangement for charging an unmanned aerialvehicle according to some aspects;

FIG. 237 shows an exemplary method for charging an unmanned aerialvehicle according to some aspects;

FIG. 238 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIG. 239 shows an exemplary network scenario in a network tracking areaaccording to some aspects;

FIG. 240 show a first exemplary message sequence chart involving a corenetwork signaling procedure according to some aspects;

FIGS. 241A and 241B show a second exemplary message sequence chartinvolving a core network signaling procedure according to some aspects;

FIG. 242 shows an exemplary network scenario in multiple networktracking areas according to some aspects;

FIG. 243 shows an exemplary message sequence chart for a core networksignaling procedure according to some aspects;

FIG. 244 shows an exemplary network scenario with a fake cell accordingto some aspects;

FIG. 245 shows an exemplary message sequence chart for a core networksignaling procedure with a fake cell according to some aspects;

FIG. 246 shows an exemplary message sequence chart for a core networksignaling procedure with a rejection according to some aspects;

FIG. 247 shows an exemplary network scenario in multiple tracking areaswith a fake cell according to some aspects;

FIG. 248 shows an exemplary internal configuration of a terminal deviceaccording to some aspects;

FIG. 249 shows an exemplary message sequence chart for a failedregistration attempt according to some aspects;

FIGS. 250A and 250B shows an exemplary message sequence chart formultiple failed registration attempts according to some aspects;

FIG. 251 shows an exemplary procedure for failed registration attemptsaccording to some aspects;

FIG. 252 shows an exemplary diagram illustrating terminal deviceregistration according to some aspects;

FIG. 253 shows a first exemplary method of operating a communicationdevice according to some aspects;

FIG. 254 shows a first exemplary method of operating a communicationdevice according to some aspects;

FIG. 255 shows a first exemplary method of operating a communicationdevice according to some aspects; and

FIG. 256 shows a first exemplary method of operating a communicationdevice according to some aspects.

DESCRIPTION

The following detailed description refers to the accompanying drawingsthat show, by way of illustration, specific details and aspects ofaspects in which the disclosure may be practiced.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration”. Any aspect or design described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs.

The words “plurality” and “multiple” in the description or the claimsexpressly refer to a quantity greater than one. The terms “group (of)”,“set [of]”, “collection (of)”, “series (of)”, “sequence (of)”, “grouping(of)”, among others, an d the like in the description or in the claimsrefer to a quantity equal to or greater than one, i.e. one or more. Anyterm expressed in plural form that does not expressly state “plurality”or “multiple” likewise refers to a quantity equal to or greater thanone. The terms “proper subset”, “reduced subset”, and “lesser subset”refer to a subset of a set that is not equal to the set, i.e. a subsetof a set that contains less elements than the set.

Any vector and/or matrix notation utilized herein is exemplary in natureand is employed solely for purposes of explanation. Accordingly, aspectsof this disclosure accompanied by vector and/or matrix notation are notlimited to being implemented solely using vectors and/or matrices, andthat the associated processes and computations may be equivalentlyperformed with respect to sets, sequences, groups, among others, ofdata, observations, information, signals, samples, symbols, elements,among others.

As used herein, “memory” are understood as a non-transitorycomputer-readable medium in which data or information can be stored forretrieval. References to “memory” included herein may thus be understoodas referring to volatile or non-volatile memory, including random accessmemory (RAM), read-only memory (ROM), flash memory, solid-state storage,magnetic tape, hard disk drive, optical drive, among others, or anycombination thereof. Furthermore, registers, shift registers, processorregisters, data buffers, among others, are also embraced herein by theterm memory. A single component referred to as “memory” or “a memory”may be composed of more than one different type of memory, and thus mayrefer to a collective component comprising one or more types of memory.Any single memory component may be separated into multiple collectivelyequivalent memory components, and vice versa. Furthermore, while memorymay be depicted as separate from one or more other components (such asin the drawings), memory may also be integrated with other components,such as on a common integrated chip or a controller with an embeddedmemory.

The term “software” refers to any type of executable instruction,including firmware.

The term “terminal device” utilized herein refers to user-side devices(both portable and fixed) that can connect to a core network and/orexternal data networks via a radio access network. “Terminal device” caninclude any mobile or immobile wireless communication device, includingUser Equipments (UEs), Mobile Stations (MSs), Stations (STAs), cellularphones, tablets, laptops, personal computers, wearables, multimediaplayback and other handheld or body-mounted electronic devices,consumer/home/office/commercial appliances, vehicles, and any otherelectronic device capable of user-side wireless communications. Withoutloss of generality, in some cases terminal devices can also includeapplication-layer components, such as application processors or othergeneral processing components, that are directed to functionality otherthan wireless communications. Terminal devices can optionally supportwired communications in addition to wireless communications.Furthermore, terminal devices can include vehicular communicationdevices that function as terminal devices.

The term “network access node” as utilized herein refers to anetwork-side device that provides a radio access network with whichterminal devices can connect and exchange information with a corenetwork and/or external data networks through the network access node.“Network access nodes” can include any type of base station or accesspoint, including macro base stations, micro base stations, NodeBs,evolved NodeBs (eNBs), Home base stations, Remote Radio Heads (RRHs),relay points, Wi-Fi/WLAN Access Points (APs), Bluetooth master devices,DSRC RSUs, terminal devices acting as network access nodes, and anyother electronic device capable of network-side wireless communications,including both immobile and mobile devices (e.g., vehicular networkaccess nodes, moving cells, and other movable network access nodes). Asused herein, a “cell” in the context of telecommunications may beunderstood as a sector served by a network access node. Accordingly, acell may be a set of geographically co-located antennas that correspondto a particular sectorization of a network access node. A network accessnode can thus serve one or more cells (or sectors), where the cells arecharacterized by distinct communication channels. Furthermore, the term“cell” may be utilized to refer to any of a macrocell, microcell,femtocell, picocell, among others Certain communication devices can actas both terminal devices and network access nodes, such as a terminaldevice that provides network connectivity for other terminal devices.

Various aspects of this disclosure may utilize or be related to radiocommunication technologies. While some examples may refer to specificradio communication technologies, the examples provided herein may besimilarly applied to various other radio communication technologies,both existing and not yet formulated, particularly in cases where suchradio communication technologies share similar features as disclosedregarding the following examples. Various exemplary radio communicationtechnologies that the aspects described herein may utilize include, butare not limited to: a Global System for Mobile Communications (GSM)radio communication technology, a General Packet Radio Service (GPRS)radio communication technology, an Enhanced Data Rates for GSM Evolution(EDGE) radio communication technology, and/or a Third GenerationPartnership Project (3GPP) radio communication technology, for exampleUniversal Mobile Telecommunications System (UMTS), Freedom of MultimediaAccess (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term EvolutionAdvanced (LTE Advanced), Code division multiple access 2000 (CDMA2000),Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G),Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD),Universal Mobile Telecommunications System (Third Generation) (UMTS(3G)), Wideband Code Division Multiple Access (Universal MobileTelecommunications System) (W-CDMA (UMTS)), High Speed Packet Access(HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed UplinkPacket Access (HSUPA), High Speed Packet Access Plus (HSPA+), UniversalMobile Telecommunications System-Time-Division Duplex (UMTS-TDD), TimeDivision-Code Division Multiple Access (TD-CDMA), TimeDivision-Synchronous Code Division Multiple Access (TD-CDMA), 3rdGeneration Partnership Project Release 8 (Pre-4th Generation) (3GPP Rel.8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9),3GPP Rel. 10 (3rd Generation Partnership Project Release 10), 3GPP Rel.11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rdGeneration Partnership Project Release 12), 3GPP Rel. 13 (3rd GenerationPartnership Project Release 13), 3GPP Rel. 14 (3rd GenerationPartnership Project Release 14), 3GPP Rel. 15 (3rd GenerationPartnership Project Release 15), 3GPP Rel. 16 (3rd GenerationPartnership Project Release 16), 3GPP Rel. 17 (3rd GenerationPartnership Project Release 17) and subsequent Releases (such as Rel.18, Rel. 19, among others), 3GPP 5G, 3GPP LTE Extra, LTE-Advanced Pro,LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial RadioAccess (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long TermEvolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G),Code division multiple access 2000 (Third generation) (CDMA2000 (3G)),Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced MobilePhone System (1st Generation) (AMPS (1G)), Total Access CommunicationSystem/Extended Total Access Communication System (TACS/ETACS), DigitalAMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), MobileTelephone System (MTS), Improved Mobile Telephone System (IMTS),Advanced Mobile Telephone System (AMTS), OLT (Norwegian for OffentligLandmobil Telefoni, Public Land Mobile Telephony), MTD (Swedishabbreviation for Mobiltelefonisystem D, or Mobile telephony system D),Public Automated Land Mobile (Autotel/PALM), ARP (Finnish forAutoradiopuhelin, “car radio phone”), NMT (Nordic Mobile Telephony),High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap),Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, IntegratedDigital Enhanced Network (iDEN), Personal Digital Cellular (PDC),Circuit Switched Data (CSD), Personal Handy-phone System (PHS), WidebandIntegrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed MobileAccess (UMA), also referred to as also referred to as 3GPP GenericAccess Network, or GAN standard), Zigbee, Bluetooth(r), Wireless GigabitAlliance (WiGig) standard, mmWave standards in general (wireless systemsoperating at 10-300 GHz and above such as WiGig, IEEE 802.11ad, IEEE802.11 ay, among others), technologies operating above 300 GHz and THzbands, (3GPP/LTE based or IEEE 802.11p and other) Vehicle-to-Vehicle(V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) andInfrastructure-to-Vehicle (12V) communication technologies, 3GPPcellular V2X, DSRC (Dedicated Short Range Communications) communicationsystems such as Intelligent-Transport-Systems and others, the EuropeanITS-G5 system (i.e. the European flavor of IEEE 802.11p based DSRC,including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequencybands dedicated to ITS for safety related applications in the frequencyrange 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITSfrequency bands dedicated to ITS non-safety applications in thefrequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITSapplications in the frequency range 5,470 GHz to 5,725 GHz)), amongothers. Aspects described herein can be used in the context of anyspectrum management scheme including dedicated licensed spectrum,unlicensed spectrum, (licensed) shared spectrum (such as LSA=LicensedShared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and furtherfrequencies and SAS=Spectrum Access System in 3.55-3.7 GHz and furtherfrequencies). Applicable spectrum bands include IMT (InternationalMobile Telecommunications) spectrum as well as other types ofspectrum/bands, such as bands with national allocation (including450-470 MHz, 902-928 MHz (e.g., allocated for example in US (FCC Part15)), 863-868.6 MHz (e.g., allocated for example in European Union (ETSIEN 300 220)), 915.9-929.7 MHz (e.g., allocated for example in Japan),917-923.5 MHz (e.g., allocated for example in South Korea), 755-779 MHzand 779-787 MHz (e.g., allocated for example in China), 790-960 MHz,1710-2025 MHz, 2110-2200 MHz, 2300-2400 MHz, 2.4-2.4835 GHz (e.g., it isan ISM band with global availability and it is used by Wi-Fi technologyfamily (11b/g/n/ax) and also by Bluetooth), 2500-2690 MHz, 698-790 MHz,610-790 MHz, 3400-3600 MHz, 3400-3800 MHz, 3.55-3.7 GHz (e.g., allocatedfor example in the US for Citizen Broadband Radio Service), 5.15-5.25GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (e.g.,allocated for example in the US (FCC part 15), consists four U-NII bandsin total 500 MHz spectrum), 5.725-5.875 GHz (e.g., allocated for examplein EU (ETSI EN 301 893)), 5.47-5.65 GHz (e.g., allocated for example inSouth Korea, 5925-7125 MHz and 5925-6425 MHz band (e.g., underconsideration in US and EU, respectively, where next generation Wi-Fisystem may also include the 6 GHz spectrum as operating band),IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range,among others), spectrum made available under FCC's “Spectrum Frontier”5G initiative (including 27.5-28.35 GHz, 29.1-29.25 GHz, 31-31.3 GHz,37-38.6 GHz, 38.6-40 GHz, 42-42.5 GHz, 57-64 GHz, 71-76 GHz, 81-86 GHzand 92-94 GHz, among others), the ITS (Intelligent Transport Systems)band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bandscurrently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz),WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) andWiGig Band 4 (63.72-65.88 GHz), 57-64/66 GHz (e.g., where this band hasnear-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig.In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHzspectrum), the 70.2 GHz-71 GHz band, any band between 65.88 GHz and 71GHz, bands currently allocated to automotive radar applications such as76-81 GHz, and future bands including 94-300 GHz and above. Furthermore,the scheme can be used on a secondary basis on bands such as the TVWhite Space bands (typically below 790 MHz) where in particular the 400MHz and 700 MHz bands are promising candidates. Besides cellularapplications, specific applications for vertical markets may beaddressed such as PMSE (Program Making and Special Events), medical,health, surgery, automotive, low-latency, drones, among othersapplications.

Aspects described herein can also implement a hierarchical applicationof the scheme is possible, e.g. by introducing a hierarchicalprioritization of usage for different types of users (e.g.,low/medium/high priority, among others), based on a prioritized accessto the spectrum e.g. with highest priority to tier-1 users, followed bytier-2, then tier-3, and so forth users. Aspects described herein canalso be applied to different Single Carrier or OFDM flavors (CP-OFDM,SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, amongothers) and in particular 3GPP NR (New Radio) by allocating the OFDMcarrier data bit vectors to the corresponding symbol resources.]. Someof the features in this disclosure are defined for the network side,such as Access Points, eNodeBs, among others In some cases, a UserEquipment (UE) may also take this role and act as an Access Points,eNodeBs, or the like. some or all features defined for network equipmentmay be implemented by a UE.

For purposes of this disclosure, radio communication technologies may beclassified as one of a Short Range radio communication technology orCellular Wide Area radio communication technology. Short Range radiocommunication technologies may include Bluetooth, WLAN (e.g., accordingto any IEEE 802.11 standard), and other similar radio communicationtechnologies. Cellular Wide Area radio communication technologies mayinclude Global System for Mobile Communications (GSM), Code DivisionMultiple Access 2000 (CDMA2000), Universal Mobile TelecommunicationsSystem (UMTS), Long Term Evolution (LTE), General Packet Radio Service(GPRS), Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSMEvolution (EDGE), High Speed Packet Access (HSPA; including High SpeedDownlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA),HSDPA Plus (HSDPA+), and HSUPA Plus (HSUPA+)), WorldwideInteroperability for Microwave Access (WiMax) (e.g., according to anIEEE 802.16 radio communication standard, e.g., WiMax fixed or WiMaxmobile), for example, and other similar radio communicationtechnologies. Cellular Wide Area radio communication technologies alsoinclude “small cells” of such technologies, such as microcells,femtocells, and picocells. Cellular Wide Area radio communicationtechnologies may be generally referred to herein as “cellular”communication technologies.

The terms “radio communication network” and “wireless network” asutilized herein encompasses both an access section of a network (e.g., aradio access network (RAN) section) and a core section of a network(e.g., a core network section). The term “radio idle mode” or “radioidle state” used herein in reference to a terminal device refers to aradio control state in which the terminal device is not allocated atleast one dedicated communication channel of a mobile communicationnetwork. The term “radio connected mode” or “radio connected state” usedin reference to a terminal device refers to a radio control state inwhich the terminal device is allocated at least one dedicated uplinkcommunication channel of a radio communication network.

Unless explicitly specified, the term “transmit” encompasses both direct(point-to-point) and indirect transmission (via one or more intermediarypoints). Similarly, the term “receive” encompasses both direct andindirect reception. Furthermore, the terms “transmit”, “receive”,“communicate”, and other similar terms encompass both physicaltransmission (e.g., the transmission of radio signals) and logicaltransmission (e.g., the transmission of digital data over a logicalsoftware-level connection). For example, a processor or controller maytransmit or receive data over a software-level connection with anotherprocessor or controller in the form of radio signals, where the physicaltransmission and reception is handled by radio-layer components such asRF transceivers and antennas, and the logical transmission and receptionover the software-level connection is performed by the processors orcontrollers. The term “communicate” encompasses one or both oftransmitting and receiving, i.e. unidirectional or bidirectionalcommunication in one or both of the incoming and outgoing directions.The term “calculate” encompass both ‘direct’ calculations via amathematical expression/formula/relationship and ‘indirect’ calculationsvia lookup or hash tables and other array indexing or searchingoperations.

General Network and Device Description

FIGS. 1 and 2 depict an exemplary network and device architecture forwireless communications. In particular, FIG. 1 shows exemplary radiocommunication network 100 according to some aspects, which may includeterminal devices 102 and 104 and network access nodes 110 and 102. Radiocommunication network 100 may communicate with terminal devices 102 and104 via network access nodes 110 and 102 over a radio access network.Although certain examples described herein may refer to a particularradio access network context (e.g., LTE, UMTS, GSM, other 3rd GenerationPartnership Project (3GPP) networks, WLAN/WiFi, Bluetooth, 5G, mmWave,etc.), these examples are demonstrative and may therefore be readilyapplied to any other type or configuration of radio access network. Thenumber of network access nodes and terminal devices in radiocommunication network 100 is exemplary and is scalable to any amount.

In an exemplary cellular context, network access nodes 110 and 102 maybe base stations (e.g., eNodeBs, NodeBs, Base Transceiver Stations(BTSs), or any other type of base station), while terminal devices 102and 104 may be cellular terminal devices (e.g., Mobile Stations (MSs),User Equipments (UEs), or any type of cellular terminal device). Networkaccess nodes 110 and 102 may therefore interface (e.g., via backhaulinterfaces) with a cellular core network such as an Evolved Packet Core(EPC, for LTE), Core Network (CN, for UMTS), or other cellular corenetworks, which may also be considered part of radio communicationnetwork 100. The cellular core network may interface with one or moreexternal data networks. In an exemplary short-range context, networkaccess node 110 and 102 may be access points (APs, e.g., WLAN or WiFiAPs), while terminal device 102 and 104 may be short range terminaldevices (e.g., stations (STAs)). Network access nodes 110 and 102 mayinterface (e.g., via an internal or external router) with one or moreexternal data networks.

Network access nodes 110 and 102 (and, optionally, other network accessnodes of radio communication network 100 not explicitly shown in FIG. 1) may accordingly provide a radio access network to terminal devices 102and 104 (and, optionally, other terminal devices of radio communicationnetwork 100 not explicitly shown in FIG. 1 ). In an exemplary cellularcontext, the radio access network provided by network access nodes 110and 102 may enable terminal devices 102 and 104 to wirelessly access thecore network via radio communications. The core network may provideswitching, routing, and transmission, for traffic data related toterminal devices 102 and 104, and may further provide access to variousinternal data networks (e.g., control nodes, routing nodes that transferinformation between other terminal devices on radio communicationnetwork 100, etc.) and external data networks (e.g., data networksproviding voice, text, multimedia (audio, video, image), and otherInternet and application data). In an exemplary short-range context, theradio access network provided by network access nodes 110 and 102 mayprovide access to internal data networks (e.g., for transferring databetween terminal devices connected to radio communication network 100)and external data networks (e.g., data networks providing voice, text,multimedia (audio, video, image), and other Internet and applicationdata).

The radio access network and core network (if applicable, such as for acellular context) of radio communication network 100 may be governed bycommunication protocols that can vary depending on the specifics ofradio communication network 100. Such communication protocols may definethe scheduling, formatting, and routing of both user and control datatraffic through radio communication network 100, which includes thetransmission and reception of such data through both the radio accessand core network domains of radio communication network 100.Accordingly, terminal devices 102 and 104 and network access nodes 110and 102 may follow the defined communication protocols to transmit andreceive data over the radio access network domain of radio communicationnetwork 100, while the core network may follow the defined communicationprotocols to route data within and outside of the core network.Exemplary communication protocols include LTE, UMTS, GSM, WiMAX,Bluetooth, WiFi, mmWave, etc., any of which may be applicable to radiocommunication network 100.

FIG. 2 shows an internal configuration of terminal device 102 accordingto some aspects, which may include antenna system 202, radio frequency(RF) transceiver 204, baseband modem 206 (including digital signalprocessor 208 and protocol controller 210), application processor 212,and memory 214. Although not explicitly shown in FIG. 2 , in someaspects terminal device 102 may include one or more additional hardwareand/or software components, such as processors/microprocessors,controllers/microcontrollers, other specialty or generichardware/processors/circuits, peripheral device(s), memory, powersupply, external device interface(s), subscriber identity module(s)(SIMs), user input/output devices (display(s), keypad(s),touchscreen(s), speaker(s), external button(s), camera(s),microphone(s), etc.), or other related components.

Terminal device 102 may transmit and receive radio signals on one ormore radio access networks. Baseband modem 206 may direct suchcommunication functionality of terminal device 102 according to thecommunication protocols associated with each radio access network, andmay execute control over antenna system 202 and RF transceiver 204 totransmit and receive radio signals according to the formatting andscheduling parameters defined by each communication protocol. Althoughvarious practical designs may include separate communication componentsfor each supported radio communication technology (e.g., a separateantenna, RF transceiver, digital signal processor, and controller), forpurposes of conciseness the configuration of terminal device 102 shownin FIG. 2 depicts only a single instance of such components.

Terminal device 102 may transmit and receive wireless signals withantenna system 202, which may be a single antenna or an antenna arraythat includes multiple antennas. In some aspects, antenna system 202 mayadditionally include analog antenna combination and/or beamformingcircuitry. In the receive (RX) path, RF transceiver 204 may receiveanalog radio frequency signals from antenna system 202 and performanalog and digital RF front-end processing on the analog radio frequencysignals to produce digital baseband samples (e.g., In-Phase/Quadrature(IQ) samples) to provide to baseband modem 206. RF transceiver 204 mayinclude analog and digital reception components including amplifiers(e.g., Low Noise Amplifiers (LNAs)), filters, RF demodulators (e.g., RFIQ demodulators)), and analog-to-digital converters (ADCs), which RFtransceiver 204 may utilize to convert the received radio frequencysignals to digital baseband samples. In the transmit (TX) path, RFtransceiver 204 may receive digital baseband samples from baseband modem206 and perform analog and digital RF front-end processing on thedigital baseband samples to produce analog radio frequency signals toprovide to antenna system 202 for wireless transmission. RF transceiver204 may thus include analog and digital transmission componentsincluding amplifiers (e.g., Power Amplifiers (PAs), filters, RFmodulators (e.g., RF IQ modulators), and digital-to-analog converters(DACs), which RF transceiver 204 may utilize to mix the digital basebandsamples received from baseband modem 206 and produce the analog radiofrequency signals for wireless transmission by antenna system 202. Insome aspects baseband modem 206 may control the radio transmission andreception of RF transceiver 204, including specifying the transmit andreceive radio frequencies for operation of RF transceiver 204.

As shown in FIG. 2 , baseband modem 206 may include digital signalprocessor 208, which may perform physical layer (PHY, Layer 1)transmission and reception processing to, in the transmit path, prepareoutgoing transmit data provided by protocol controller 210 fortransmission via RF transceiver 204, and, in the receive path, prepareincoming received data provided by RF transceiver 204 for processing byprotocol controller 210. Digital signal processor 208 may be configuredto perform one or more of error detection, forward error correctionencoding/decoding, channel coding and interleaving, channelmodulation/demodulation, physical channel mapping, radio measurement andsearch, frequency and time synchronization, antenna diversityprocessing, power control and weighting, rate matching/de-matching,retransmission processing, interference cancelation, and any otherphysical layer processing functions. Digital signal processor 208 may bestructurally realized as hardware components (e.g., as one or moredigitally-configured hardware circuits or FPGAs), software-definedcomponents (e.g., one or more processors configured to execute programcode defining arithmetic, control, and I/O instructions (e.g., softwareand/or firmware) stored in a non-transitory computer-readable storagemedium), or as a combination of hardware and software components. Insome aspects, digital signal processor 208 may include one or moreprocessors configured to retrieve and execute program code that definescontrol and processing logic for physical layer processing operations.In some aspects, digital signal processor 208 may execute processingfunctions with software via the execution of executable instructions. Insome aspects, digital signal processor 208 may include one or morededicated hardware circuits (e.g., ASICs, FPGAs, and other hardware)that are digitally configured to specific execute processing functions,where the one or more processors of digital signal processor 208 mayoffload certain processing tasks to these dedicated hardware circuits,which are known as hardware accelerators. Exemplary hardwareaccelerators can include Fast Fourier Transform (FFT) circuits andencoder/decoder circuits. In some aspects, the processor and hardwareaccelerator components of digital signal processor 208 may be realizedas a coupled integrated circuit.

Terminal device 102 may be configured to operate according to one ormore radio communication technologies. Digital signal processor 208 maybe responsible for lower-layer processing functions (e.g., Layer 1/PHY)of the radio communication technologies, while protocol controller 210may be responsible for upper-layer protocol stack functions (e.g., DataLink Layer/Layer 2 and/or Network Layer/Layer 3). Protocol controller210 may thus be responsible for controlling the radio communicationcomponents of terminal device 102 (antenna system 202, RF transceiver204, and digital signal processor 208) in accordance with thecommunication protocols of each supported radio communicationtechnology, and accordingly may represent the Access Stratum andNon-Access Stratum (NAS) (also encompassing Layer 2 and Layer 3) of eachsupported radio communication technology. Protocol controller 210 may bestructurally embodied as a processor configured to execute protocolstack software (retrieved from a controller memory) and subsequentlycontrol the radio communication components of terminal device 102 totransmit and receive communication signals in accordance with thecorresponding protocol stack control logic defined in the protocol stacksoftware. Protocol controller 210 may include one or more processorsconfigured to retrieve and execute program code that defines theupper-layer protocol stack logic for one or more radio communicationtechnologies, which can include Data Link Layer/Layer 2 and NetworkLayer/Layer 3 functions. Protocol controller 210 may be configured toperform both user-plane and control-plane functions to facilitate thetransfer of application layer data to and from radio terminal device 102according to the specific protocols of the supported radio communicationtechnology. User-plane functions can include header compression andencapsulation, security, error checking and correction, channelmultiplexing, scheduling and priority, while control-plane functions mayinclude setup and maintenance of radio bearers. The program coderetrieved and executed by protocol controller 210 may include executableinstructions that define the logic of such functions.

In some aspects, terminal device 102 may be configured to transmit andreceive data according to multiple radio communication technologies.Accordingly, in some aspects one or more of antenna system 202, RFtransceiver 204, digital signal processor 208, and protocol controller210 may include separate components or instances dedicated to differentradio communication technologies and/or unified components that areshared between different radio communication technologies. For example,in some aspects protocol controller 210 may be configured to executemultiple protocol stacks, each dedicated to a different radiocommunication technology and either at the same processor or differentprocessors. In some aspects, digital signal processor 208 may includeseparate processors and/or hardware accelerators that are dedicated todifferent respective radio communication technologies, and/or one ormore processors and/or hardware accelerators that are shared betweenmultiple radio communication technologies. In some aspects, RFtransceiver 204 may include separate RF circuitry sections dedicated todifferent respective radio communication technologies, and/or RFcircuitry sections shared between multiple radio communicationtechnologies. In some aspects, antenna system 202 may include separateantennas dedicated to different respective radio communicationtechnologies, and/or antennas shared between multiple radiocommunication technologies. Accordingly, while antenna system 202, RFtransceiver 204, digital signal processor 208, and protocol controller210 are shown as individual components in FI, in some aspects antennasystem 202, RF transceiver 204, digital signal processor 208, and/orprotocol controller 210 can encompass separate components dedicated todifferent radio communication technologies.

Terminal device 102 may also include application processor 212 andmemory 214. Application processor 212 may be a CPU, and may beconfigured to handle the layers above the protocol stack, including thetransport and application layers. Application processor 212 may beconfigured to execute various applications and/or programs of terminaldevice 102 at an application layer of terminal device 102, such as anoperating system (OS), a user interface (UI) for supporting userinteraction with terminal device 102, and/or various user applications.The application processor may interface with baseband modem 206 and actas a source (in the transmit path) and a sink (in the receive path) foruser data, such as voice data, audioNideamage data, messaging data,application data, basic Internet/web access data, etc. In the transmitpath, protocol controller 210 may therefore receive and process outgoingdata provided by application processor 212 according to thelayer-specific functions of the protocol stack, and provide theresulting data to digital signal processor 208. Digital signal processor208 may then perform physical layer processing on the received data toproduce digital baseband samples, which digital signal processor mayprovide to RF transceiver 204. RF transceiver 204 may then process thedigital baseband samples to convert the digital baseband samples toanalog RF signals, which RF transceiver 204 may wirelessly transmit viaantenna system 202. In the receive path, RF transceiver 204 may receiveanalog RF signals from antenna system 202 and process the analog RFsignals to obtain digital baseband samples. RF transceiver 204 mayprovide the digital baseband samples to digital signal processor 208,which may perform physical layer processing on the digital basebandsamples. Digital signal processor 208 may then provide the resultingdata to protocol controller 210, which may process the resulting dataaccording to the layer-specific functions of the protocol stack andprovide the resulting incoming data to application processor 212.Application processor 212 may then handle the incoming data at theapplication layer, which can include execution of one or moreapplication programs with the data and/or presentation of the data to auser via a user interface.

Memory 214 may embody a memory component of terminal device 102, such asa hard drive or another such permanent memory device. Although notexplicitly depicted in FIG. 2 , the various other components of terminaldevice 102 shown in FIG. 2 may additionally each include integratedpermanent and non-permanent and/or volatile & non-volatile memorycomponents, such as for storing software program code, buffering data,etc.

In accordance with some radio communication networks, terminal devices102 and 104 may execute mobility procedures to connect to, disconnectfrom, and switch between available network access nodes of the radioaccess network of radio communication network 100. As each networkaccess node of radio communication network 100 may have a specificcoverage area, terminal devices 102 and 104 may be configured to selectand re-select between the available network access nodes in order tomaintain a strong radio access connection with the radio access networkof radio communication network 100. For example, terminal device 102 mayestablish a radio access connection with network access node 110 whileterminal device 104 may establish a radio access connection with networkaccess node 112. In the event that the current radio access connectiondegrades, terminal devices 102 or 104 may seek a new radio accessconnection with another network access node of radio communicationnetwork 100; for example, terminal device 104 may move from the coveragearea of network access node 112 into the coverage area of network accessnode 110. As a result, the radio access connection with network accessnode 112 may degrade, which terminal device 104 may detect via radiomeasurements such as signal strength, signal quality, or errorrate-related measurements of network access node 112. Depending on themobility procedures defined in the appropriate network protocols forradio communication network 100, terminal device 104 may seek a newradio access connection (which may be, for example, triggered atterminal device 104 or by the radio access network), such as byperforming radio measurements on neighboring network access nodes todetermine whether any neighboring network access nodes can provide asuitable radio access connection. As terminal device 104 may have movedinto the coverage area of network access node 110, terminal device 104may identify network access node 110 (which may be selected by terminaldevice 104 or selected by the radio access network) and transfer to anew radio access connection with network access node 110. Such mobilityprocedures, including radio measurements, cell selection/reselection,and handover are established in the various network protocols and may beemployed by terminal devices and the radio access network in order tomaintain strong radio access connections between each terminal deviceand the radio access network across any number of different radio accessnetwork scenarios.

FIG. 3 shows an exemplary internal configuration of a network accessnode, such as network access node 110, according to some aspects. Asshown in FIG. 3 , network access node 110 may include antenna system302, radio transceiver 304, and baseband subsystem 306 (includingphysical layer processor 308 and protocol controller 310). In anabridged overview of the operation of network access node 110, networkaccess node 110 may transmit and receive wireless signals via antennasystem 302, which may be an antenna array including multiple antennas.Radio transceiver 304 may perform transmit and receive RF processing toconvert outgoing baseband samples from baseband subsystem 306 intoanalog radio signals to provide to antenna system 302 for radiotransmission and to convert incoming analog radio signals received fromantenna system 302 into baseband samples to provide to basebandsubsystem 306. Physical layer processor 308 may be configured to performtransmit and receive PHY processing on baseband samples received fromradio transceiver 304 to provide to controller 310 and on basebandsamples received from controller 310 to provide to radio transceiver304. Controller 310 may control the communication functionality ofnetwork access node 110 according to the corresponding radiocommunication technology protocols, which may include exercising controlover antenna system 302, radio transceiver 304, and physical layerprocessor 308. Each of radio transceiver 304, physical layer processor308, and controller 310 may be structurally realized with hardware(e.g., with one or more digitally-configured hardware circuits orFPGAs), as software (e.g., as one or more processors executing programcode defining arithmetic, control, and I/O instructions stored in anon-transitory computer-readable storage medium), or as a mixedcombination of hardware and software. In some aspects, radio transceiver304 may be a radio transceiver including digital and analog radiofrequency processing and amplification circuitry. In some aspects, radiotransceiver 304 may be a software-defined radio (SDR) componentimplemented as a processor configured to execute software-definedinstructions that specify radio frequency processing routines. In someaspects, physical layer processor 308 may include a processor and one ormore hardware accelerators, wherein the processor is configured tocontrol physical layer processing and offload certain processing tasksto the one or more hardware accelerators. In some aspects, controller310 may be a controller configured to execute software-definedinstructions that specify upper-layer control functions. In someaspects, controller 310 may be limited to radio communication protocolstack layer functions, while in other aspects controller 310 may also beconfigured for transport, internet, and application layer functions.

Network access node 110 may thus provide the functionality of networkaccess nodes in radio communication networks by providing a radio accessnetwork to enable served terminal devices to access communication data.For example, network access node 110 may also interface with a corenetwork, one or more other network access nodes, or various other datanetworks and servers via a wired or wireless backhaul interface.

As previously indicated, network access nodes 112 and 114 may interfacewith a core network. FIG. 4 shows an exemplary configuration inaccordance with some aspects where network access node 110 interfaceswith core network 402, which may be, for example, a cellular corenetwork. Core network 402 may provide a variety of functions to manageoperation of radio communication network 100, such as data routing,authenticating and managing users/subscribers, interfacing with externalnetworks, and various other network control tasks. Core network 402 maytherefore provide an infrastructure to route data between terminaldevice 104 and various external networks such as data network 404 anddata network 406. Terminal device 104 may thus rely on the radio accessnetwork provided by network access node 110 to wirelessly transmit andreceive data with network access node 110, which may then provide thedata to core network 402 for further routing to external locations suchas data networks 404 and 406 (which may be packet data networks (PDNs)).Terminal device 104 may therefore establish a data connection with datanetwork 404 and/or data network 406 that relies on network access node110 and core network 402 for data transfer and routing.

Terminal devices may in some cases be configured as vehicularcommunication devices (or other movable communication devices). FIG. 5shows an exemplary internal configuration of a vehicular communicationdevice 500 according to some aspects. As shown in FIG. 5 , vehicularcommunication device 500 may include steering and movement system 502,radio communication arrangement 504, and antenna system 506. One or morecomponents of vehicular communication device 500 may be arranged arounda vehicular housing of vehicular communication device 500, mounted on oroutside of the vehicular housing, enclosed within the vehicular housing,and/or any other arrangement relative to the vehicular housing where thecomponents move with vehicular communication device 500 as it travels.The vehicular housing, such as an automobile body, plane or helicopterfuselage, boat hull, or similar type of vehicular body dependent on thetype of vehicle that vehicular communication device 500 is. Steering andmovement system 502 may include components of vehicular communicationdevice 500 related to steering and movement of vehicular communicationdevice 500. In some aspects where vehicular communication device 500 isan automobile, steering and movement system 502 may include wheels andaxles, an engine, a transmission, brakes, a steering wheel, associatedelectrical circuitry and wiring, and any other components used in thedriving of an automobile. In some aspects where vehicular communicationdevice 500 is an aerial vehicle, steering and movement system 502 mayinclude one or more of rotors, propellers, jet engines, wings, ruddersor wing flaps, air brakes, a yoke or cyclic, associated electricalcircuitry and wiring, and any other components used in the flying of anaerial vehicle. In some aspects where vehicular communication device 500is an aquatic or sub-aquatic vehicle, steering and movement system 502may include any one or more of rudders, engines, propellers, a steeringwheel, associated electrical circuitry and wiring, and any othercomponents used in the steering or movement of an aquatic vehicle. Insome aspects, steering and movement system 502 may also includeautonomous driving functionality, and accordingly may also include acentral processor configured to perform autonomous driving computationsand decisions and an array of sensors for movement and obstacle sensing.The autonomous driving components of steering and movement system 502may also interface with radio communication arrangement 504 tofacilitate communication with other nearby vehicular communicationdevices and/or central networking components that perform decisions andcomputations for autonomous driving.

Radio communication arrangement 504 and antenna system 506 may performthe radio communication functionalities of vehicular communicationdevice 500, which can include transmitting and receiving communicationswith a radio communication network and/or transmitting and receivingcommunications directly with other vehicular communication devices andterminal devices. For example, radio communication arrangement 504 andantenna system 506 may be configured to transmit and receivecommunications with one or more network access nodes, such as, in theexemplary context of Dedicated Short Range Communications (DSRC) and LTEVehicle to Vehicle (V2V)/Vehicle to Everything (V2X), Roadside Units(RSUs) and base stations.

FIG. 6 shows an exemplary internal configuration of antenna system 506and radio communication arrangement 504 according to some aspects. Asshown in FIG. 6 , radio communication arrangement 504 may include RFtransceiver 602, digital signal processor 604, and controller 606.Although not explicitly shown in FIG. 6 , in some aspects radiocommunication arrangement 504 may include one or more additionalhardware and/or software components (such as processors/microprocessors,controllers/microcontrollers, other specialty or generichardware/processors/circuits, etc.), peripheral device(s), memory, powersupply, external device interface(s), subscriber identity module(s)(SIMs), user input/output devices (display(s), keypad(s),touchscreen(s), speaker(s), external button(s), camera(s),microphone(s), etc.), or other related components.

Controller 606 may be responsible for execution of upper-layer protocolstack functions, while digital signal processor 604 may be responsiblefor physical layer processing. RF transceiver 602 may be responsible forRF processing and amplification related to transmission and reception ofwireless radio signals via antenna system 506.

Antenna system 506 may be a single antenna or an antenna array thatincludes multiple antennas. Antenna system 506 may additionally includeanalog antenna combination and/or beamforming circuitry. In the receive(RX) path, RF transceiver 602 may receive analog radio signals fromantenna system 506 and perform analog and digital RF front-endprocessing on the analog radio signals to produce baseband samples(e.g., In-Phase/Quadrature (IQ) samples) to provide to digital signalprocessor 604. In some aspects, RF transceiver 602 can include analogand digital reception components such as amplifiers (e.g., a Low NoiseAmplifiers (LNAs)), filters, RF demodulators (e.g., RF IQdemodulators)), and analog-to-digital converters (ADCs), which RFtransceiver 602 may utilize to convert the received radio signals tobaseband samples. In the transmit (TX) path, RF transceiver 602 mayreceive baseband samples from digital signal processor 604 and performanalog and digital RF front-end processing on the baseband samples toproduce analog radio signals to provide to antenna system 506 forwireless transmission. In some aspects, RF transceiver 602 can includeanalog and digital transmission components such as amplifiers (e.g.,Power Amplifiers (PAs), filters, RF modulators (e.g., RF IQ modulators),and digital-to-analog converters (DACs) to mix the baseband samplesreceived from baseband modem 206, which RF transceiver 602 may use toproduce the analog radio signals for wireless transmission by antennasystem 506.

Digital signal processor 604 may be configured to perform physical layer(PHY) transmission and reception processing to, in the transmit path,prepare outgoing transmit data provided by controller 606 fortransmission via RF transceiver 602, and, in the receive path, prepareincoming received data provided by RF transceiver 602 for processing bycontroller 606. Digital signal processor 604 may be configured toperform one or more of error detection, forward error correctionencoding/decoding, channel coding and interleaving, channelmodulation/demodulation, physical channel mapping, radio measurement andsearch, frequency and time synchronization, antenna diversityprocessing, power control and weighting, rate matching/de-matching,retransmission processing, interference cancelation, and any otherphysical layer processing functions. Digital signal processor 604 mayinclude one or more processors configured to retrieve and executeprogram code that algorithmically defines control and processing logicfor physical layer processing operations. In some aspects, digitalsignal processor 604 may execute processing functions with software viathe execution of executable instructions. In some aspects, digitalsignal processor 604 may include one or more hardware accelerators,where the one or more processors of digital signal processor 604 mayoffload certain processing tasks to these hardware accelerators. In someaspects, the processor and hardware accelerator components of digitalsignal processor 604 may be realized as a coupled integrated circuit.

While digital signal processor 604 may be responsible for lower-layerphysical processing functions, controller 606 may be responsible forupper-layer protocol stack functions. Controller 606 may include one ormore processors configured to retrieve and execute program code thatalgorithmically defines the upper-layer protocol stack logic for one ormore radio communication technologies, which can include Data LinkLayer/Layer 2 and Network Layer/Layer 3 functions. Controller 606 may beconfigured to perform both user-plane and control-plane functions tofacilitate the transfer of application layer data to and from radiocommunication arrangement 504 according to the specific protocols of thesupported radio communication technology. User-plane functions caninclude header compression and encapsulation, security, error checkingand correction, channel multiplexing, scheduling and priority, whilecontrol-plane functions may include setup and maintenance of radiobearers. The program code retrieved and executed by controller 606 mayinclude executable instructions that define the logic of such functions.

In some aspects, controller 606 may be coupled to an applicationprocessor, which may handle the layers above the protocol stackincluding transport and application layers. The application processormay act as a source for some outgoing data transmitted by radiocommunication arrangement 504 and a sink for some incoming data receivedby radio communication arrangement 504. In the transmit path, controller606 may therefore receive and process outgoing data provided by theapplication processor according to the layer-specific functions of theprotocol stack, and provide the resulting data to digital signalprocessor 604. Digital signal processor 604 may then perform physicallayer processing on the received data to produce baseband samples, whichdigital signal processor may provide to RF transceiver 602. RFtransceiver 602 may then process the baseband samples to convert thebaseband samples to analog radio signals, which RF transceiver 602 maywirelessly transmit via antenna system 506. In the receive path, RFtransceiver 602 may receive analog radio signals from antenna system 506and process the analog RF signal to obtain baseband samples. RFtransceiver 602 may provide the baseband samples to digital signalprocessor 604, which may perform physical layer processing on thebaseband samples. Digital signal processor 604 may then provide theresulting data to controller 606, which may process the resulting dataaccording to the layer-specific functions of the protocol stack andprovide the resulting incoming data to the application processor.

In some aspects, radio communication arrangement 504 may be configuredto transmit and receive data according to multiple radio communicationtechnologies. Accordingly, in some aspects one or more of antenna system506, RF transceiver 602, digital signal processor 604, and controller606 may include separate components or instances dedicated to differentradio communication technologies and/or unified components that areshared between different radio communication technologies. For example,in some aspects controller 606 may be configured to execute multipleprotocol stacks, each dedicated to a different radio communicationtechnology and either at the same processor or different processors. Insome aspects, digital signal processor 604 may include separateprocessors and/or hardware accelerators that are dedicated to differentrespective radio communication technologies, and/or one or moreprocessors and/or hardware accelerators that are shared between multipleradio communication technologies. In some aspects, RF transceiver 602may include separate RF circuitry sections dedicated to differentrespective radio communication technologies, and/or RF circuitrysections shared between multiple radio communication technologies. Insome aspects, antenna system 506 may include separate antennas dedicatedto different respective radio communication technologies, and/orantennas shared between multiple radio communication technologies.Accordingly, while antenna system 506, RF transceiver 602, digitalsignal processor 604, and controller 606 are shown as individualcomponents in FIG. 6 , in some aspects antenna system 506, RFtransceiver 602, digital signal processor 604, and/or controller 606 canencompass separate components dedicated to different radio communicationtechnologies.

Trajectory Control for Forward Sensing/Access and Backhaul Moving Cells

Many radio access networks deploy their cells as stationary entities.Examples include base stations deployed at fixed locations throughout amobile broadband coverage area and access points placed at a fixedlocation in a residential or commercial are. Given their fixedlocations, these cells may not be able to move to dynamically respond tothe positioning of their served terminal devices. While various types ofaerial cells (such as cell-equipped drones) have been proposed, theseaerial cells are still developing.

In accordance with aspects of this disclosure, a set of moving cellsproviding sensing, access, and/or backhaul services may optimize theirpositioning within a coverage area. As further described herein, in someaspects, there may be a set of backhaul moving cells that providebackhaul to outer moving cells, where trajectories of both the backhauland outer moving cells can be controlled by a central trajectorycontroller. In other aspects, the set of backhaul moving cells mayprovide backhaul to end devices (e.g., outer moving cells or terminaldevices) that do not have trajectories which are controllable by thecentral controller.

FIG. 7 shows an exemplary network diagram according to some aspects,which relates to aspects where there are both backhaul and outer movingcells with trajectories that are controllable by a central trajectorycontroller. As shown in FIG. 7 , a set of outer moving cells 702-706 maybe configured to perform an outer task for their respective targetareas. The outer task can be sensing, where the outer moving cells702-706 perform sensing with local sensors (e.g., audio, video, image,position, radar, light, environmental, or any other type of sensingcomponent) to obtain sensing data for their respective target areas.Additionally or alternatively, the outer task can be access, where outermoving cells 702-706 provide fronthaul access to terminal devices (asshown in FIG. 7 ) located in their respective target areas. In someaspects, each of moving cells 702-706 may perform the same outer task,while in other aspects some of moving cells 702-706 may performdifferent outer tasks (e.g., some perform sensing while others performaccess). The number of outer moving cells in FIG. 7 is exemplary and isscalable to any quantity.

The outer moving cells 702-706 may generate uplink data for transmissionback to the network. In the case of sensing outer moving cells, thesensing outer moving cells may generate sensing data that is sent backto a server for storage and/or processing (e.g., to evaluate andinterpret the sensing data, such as for surveillance/monitoring, controlof moving vehicles, or other analytics). In the case of access outermoving cells, their respectively served terminal devices may generatecommunication data (e.g., control and user data) that is sent back tothe radio access, core, and/or external data networks. This sensing andcommunication data may be the uplink data.

As shown in FIG. 7 , outer moving cells 702-706 may use backhaul movingcells 708 and 710 for backhaul. Accordingly, outer moving cells 702-706may transmit their uplink data to backhaul moving cells 708 and 710 onfronthaul links 716-720. Backhaul moving cells 708 and 710 may thenreceive this uplink data and transmit the uplink data to network accessnode 712 on backhaul links 722 and 724 (e.g., may relay the uplink datato network access node 712, which can include any type of relayingscheme including those with decoding and error correction). Networkaccess node 712 may then use and/or route the uplink data asappropriate. For example, network access node 712 may locally use uplinkcommunication data related to access stratum control data (e.g., at itsprotocol stack), route uplink communication data related to non-accessstratum control data to core network control nodes, and route sensingdata and uplink communication data through the core network on the pathtowards its destination (e.g., a cloud server for processing sensingdata, or an external data network associated with user data). In someaspects, network access node 712 may be stationary, while in otheraspects network access node 712 may be mobile. The number of backhaulmoving cells in FIG. 7 is exemplary and is scalable to any quantity.

The positions of outer moving cells 702-706 and backhaul moving cells708 and 710 could impact communication and/or sensing performance. Forexample, when performing sensing or access, outer moving cells 702-706may each have target areas to perform sensing on or to provide access to(where their respective target areas can be geographically fixed ordynamic). Outer moving cells 702-706 may therefore not be completelyfree to move to any location, as they may be expected to stay at aposition that allows them to effectively serve their respective targetareas. However, in some cases the optimal position to serve the targetarea may not be the optimal position to transmit uplink data to backhaulmoving cells 708-710. This can occur, for example, when theline-of-sight (LOS) path from the optimal serving position to backhaulmoving cells 708 and 710 is blocked by some object, or when the optimalserving position is far from backhaul moving cells 708 and 710. Thiscould in turn lead to low link strength for fronthaul links 712-720.

Backhaul moving cells 708 and 710 may experience similar positioningissues. For example, as shown in FIG. 7 , backhaul moving cell 710 mayprovide backhaul to outer moving cells 704 and 706. As outer movingcells 704 and 706 serve different target areas, they may be located indifferent positions. The optimal backhaul position for backhaul movingcell 710 to serve outer moving cell 704 (e.g., a position that maximizeslink strength for fronthaul link 718), however, is unlikely to be thesame as the optimal backhaul position for backhaul moving cell 710 toserve outer moving cell 706 (e.g., a position that optimizes fronthaullink 720). Furthermore, even though backhaul moving cell 710 may be ableto obtain better reception performance from outer moving cells 704 and706 when positioned closer to them, this positioning may mean thatbackhaul moving cell 710 is located far from network access node 712.The relaying transmission from backhaul moving cell 710 to networkaccess node 712 may therefore suffer with this positioning, as backhaullinks 722 and 724 may be longer in distance.

Accordingly, as shown in FIG. 7 , central trajectory controller 714 mayalso be deployed as part of the network architecture. In some aspectscentral trajectory controller 714 may be deployed as part of networkaccess node 712. In other aspects, central trajectory controller 714 maybe deployed separately and could be proximate to network access node712, such as in a Mobile Edge Computing (MEC) platform. In otheraspects, central trajectory controller 714 may be deployed as a serverin the core network, or as a server in an external data network (e.g.,part of the Internet or cloud). Although shown as a single component ofFIG. 7 , in some aspects central trajectory controller 714 may bedeployed as multiple separate physical components that are logicallyinterconnected with each other to form a virtualized central trajectorycontroller.

As will be described, central trajectory controller 714 may beconfigured to determine trajectories (e.g., fixed position or dynamicmovement path) for outer moving cells 702-706 and backhaul moving cells708 and 710. Outer moving cells 702-706 and backhaul moving cells 708and 710 may cooperate in this trajectory determination to locallyoptimize their trajectories. As used herein, the term “optimize” refersto attempting to move towards an optimal value and/or reaching anoptimal value, and may or may not include actually reaching the optimalvalue. Optimizing thus includes incrementing a function towards amaximum value (e.g., a local or absolute maximum value) or decrementinga function towards a minimum value (e.g., a local or absolute minimumvalue), such as by using incremental or decremental steps. As furtherdescribed below, the underlying logic of this trajectory determinationcan be embodied in trajectory algorithms, where central trajectorycontroller 714 may execute a central trajectory algorithm, outer movingcells 702-706 may execute an outer trajectory algorithm, and backhaulmoving cells 708-710 may execute a backhaul trajectory algorithm. Thesetrajectory algorithms can determine trajectories for outer moving cells702-706 and backhaul moving cells 708-710 may therefore be based onmultiple factors, such as the current locations of outer moving cells702-706 and their respective target areas, the current locations ofbackhaul moving cells 708 and 710 and their respective target areas, thelocation of network access node 712, and the channel conditions andtransmit capabilities of the involved devices. The logic of thesetrajectory algorithms is described in detail below.

FIGS. 8-10 show exemplary internal configurations of outer moving cells702-706, backhaul moving cells 708 and 710 and central trajectorycontroller 714 according to some aspects. With initial reference to FIG.8 , outer moving cells 702-706 may include antenna system 802, radiotransceiver 804, baseband subsystem 806 (including physical layerprocessor 808 and protocol controller 810), trajectory platform 812, andmovement system 822. Antenna system 802, radio transceiver 804, andbaseband subsystem 806 may be configured in a similar or same manner asantenna system 302, radio transceiver 304, and baseband subsystem 306 asshown and described for network access node 110 in FIG. 3 . Antennasystem 802, radio transceiver 804, and baseband subsystem 806 maytherefore be configured to perform radio communications to and fromouter moving cells 702-706, which can include wirelessly communicatingwith other moving cells, terminal devices, and network access nodes.

Trajectory platform 812 may be responsible for determining thetrajectories of outer moving cells 702-706, including communicating withother moving cells and central trajectory controller 714 to obtain inputdata and executing an outer trajectory algorithm on the input data toobtain trajectories for outer moving cells 702-706. As shown in FIG. 8 ,trajectory platform 812 may include central interface 814, cellinterface 816, and trajectory processor 818, and outer task subsystem820. In some aspects, central interface 814 and cell interface 816 mayeach be application-layer processors that are configured to transmit andreceive data (on logical software-level connections) with centraltrajectory processor 714 and other moving cells, respectively. Forexample, when transmitting data to central trajectory controller 714,central interface 814 may be configured to generate packets from thedata (e.g., according to a predefined format used by central interface814 and its peer interface at central trajectory controller 714) andprovide the packets to the protocol stack running at protocol controller810. Protocol controller 810 and physical layer processor 808 may thenprocess the packets according to the protocol stack and physical layerprotocols and transmit the data as wireless radio signals via radiotransceiver 804 and antenna system 802. When receiving data from centraltrajectory controller 714, antenna system 802 and radio transceiver 804may receive the data in the form of wireless radio signals, and providecorresponding baseband data to baseband modem. Physical layer processor808 and protocol controller 810 may then process the baseband data torecover packets transmitted by the peer interface at central trajectorycontroller 714, which protocol controller 810 may provide to centralinterface 814. Cell interface 816 may similarly transmit data to a peerinterface at other moving cells.

Trajectory processor 818 may be a processor configured to execute anouter trajectory algorithm that determines the trajectory for outermoving cells 702-706. As used herein, trajectories can refer to staticpositions, sequences of static positions (e.g., a time-stamped sequenceof static positions), or paths or contours. Trajectory processor 818 maybe configured to retrieve executable instructions defining the outertrajectory algorithm from a memory (not explicitly shown) and to executethese instructions. Trajectory processor 818 may be configured toexecute the outer trajectory algorithm on input data to determineupdated trajectories for outer moving cells 702-706. The logic of thisouter trajectory algorithm is described herein both in prose below andvisually by the drawings.

Outer task subsystem 820 may be configured to perform the outer task forouter moving cells 702-706. In some aspects where outer moving cells702-706 are configured to perform sensing, outer task subsystem 820 mayinclude one or more sensors. These sensors can be, without limitation,audio, video, image, position, radar, light, environmental, or anothertype of sensor. Outer task subsystem 820 may also include at least oneprocessor configured to provide sensing data obtained from the sensorsto baseband subsystem 806 for transmission. In some aspects where outermoving cells 702-706 are configured to provide access to terminaldevices, outer task subsystem 820 may include one or more processorsconfigured to transmit, receive, and relay data from the terminaldevices (via baseband subsystem 806, which may handle the protocol stackand physical layer communication functionality). While FIG. 8 showsouter task subsystem 820 as part of trajectory platform 812, in someaspects outer task subsystem 820 may be included as part of basebandsubsystem 806.

Movement system 822 may be responsible for controlling and executingmovement of outer moving cells 702-706. As shown in FIG. 8 , movementsystem 822 may include movement controller 824 and steering and movementmachinery 826. Movement controller 824 may be configured to control theoverall movement of outer moving cells 702-706 (e.g., through executionof a movement control function), and may provide control signals tosteering and movement machinery 826 that specify the movement. In someaspects, movement controller 824 may be autonomous, and therefore may beconfigured to execute an autonomous movement control function wheremovement controller 824 directs movement of outer moving cells 702-706without primary human/operator control. Steering and movement machinery826 may then execute the movement specified in the control signals. Insome aspects where outer moving cells 702-706 are terrestrial vehicles,steering and movement machinery 826 may include, for example, wheels andaxles, an engine, a transmission, brakes, a steering wheel, associatedelectrical circuitry and wiring, and any other components used in thedriving of an automobile or other land-based vehicle. In some aspectswhere outer moving cells 702-706 are aerial vehicles, including but notlimited to drones, steering and movement machinery 826 may include, forexample, one or more of rotors, propellers, jet engines, wings, ruddersor wing flaps, air brakes, a yoke or cyclic, associated electricalcircuitry and wiring, and any other components used in the flying of anaerial vehicle. In some aspects where outer moving cells 702-706 areaquatic or sub-aquatic vehicles, steering and movement machinery 826 mayinclude, for example, any one or more of rudders, engines, propellers, asteering wheel, associated electrical circuitry and wiring, and anyother components used in the steering or movement of an aquatic vehicle.

FIG. 9 shows an exemplary internal configuration of backhaul movingcells 708 and 710 according to some aspects. As shown in FIG. 9 ,backhaul moving cells 708 and 710 may include similar components toouter moving cells 702-706. Antenna system 902, radio transceiver 904,baseband subsystem 906, central interface 914, cell interface 916,movement controller 924, and steering and movement machinery 926 may berespectively configured in the manner of antenna system 802, radiotransceiver 804, baseband subsystem 806, central interface 814, cellinterface 816, movement controller 824, and steering and movementmachinery 826 as shown and described for FIG. 8 .

Trajectory processor 918 may be configured to execute a backhaultrajectory algorithm that controls the trajectory of backhaul movingcells 708 and 710. This backhaul trajectory algorithm is describedherein in prose and visually by the figures.

As shown in FIG. 9 , backhaul moving cells 708 and 710 may also includerelay router 920. As previously indicated, backhaul moving cells 708 and710 may be configured to provide backhaul services to outer moving cells702-706, which can include receiving uplink data from outer moving cells702-706 (on fronthaul links 716-720) and relaying the uplink data to theradio access network (e.g., to network access node 712 on backhaul links722 and 724). Relay router 920 may be configured to handle this relayingfunctionality, and may interact with cell interface 916 to identify theuplink data for relaying and subsequently transmit the uplink data tothe radio access network via baseband subsystem 906. Although shown aspart of trajectory platform 912 in FIG. 9 , in some aspects relay router920 may also be part (e.g., fully or partially) of baseband subsystem906.

FIG. 10 shows an exemplary internal configuration of central trajectorycontroller 714 according to some aspects. As shown in FIG. 10 , centraltrajectory controller 714 may include cell interface 1002, input datarepository 1004, and trajectory processor 1006. In some aspects, cellinterface 1002 may be an application-layer processor configured totransmit and receive data (on logical software-level connections) withits peer central interfaces 814 and 914 in outer moving cells 702-706and backhaul moving cells 708 and 710. Cell interface 1002 may thereforesend packets on the interface shown in FIG. 10 , which may pass throughan Internet backhaul, core network, and/or radio access network(depending on the deployment location of central trajectory controller714). The radio access network (e.g., network access node 712) maytransmit the packets as wireless radio signals. Outer moving cells702-706 and backhaul moving cells 708 and 710 may be configured toreceive and process the wireless radio signals to recover the datapackets at their peer central interfaces 814 and 914.

Input data repository 1004 may be a server-type component including acontroller and a memory. Input data repository 1004 may be configured tocollect input data for input to a central trajectory algorithm executedby trajectory processor 1006. The central trajectory algorithm may beconfigured to determine coarse trajectories for outer moving cells702-706 and backhaul moving cells 708 and 710. These coarse trajectoriesmay be the high-level, planned trajectories provided by centraltrajectory controller 714, and may be determined by central trajectorycontroller 714 to optimize the fronthaul and backhaul links provided bybackhaul moving cells 708 and 710 while also enabling outer moving cells702-706 to perform their respective forward tasks. Outer moving cells702-706 and backhaul moving cells 708 and 710 may refine these coarsetrajectories using their outer and backhaul trajectory algorithms toobtain updated trajectories. In some aspects, the central trajectoryalgorithm may also be configured to determine initial routings for outermoving cells 702-706 and backhaul moving cells 708 and 710. Theseinitial routings may specify the backhaul path between outer movingcells 702-706 and the radio access network via backhaul moving cells 708and 710, or in other words, which of backhaul moving cells 708 and 710outer moving cells 702-706 should transmit their uplink data to. Thiscentral trajectory algorithm is described herein in prose and visuallyby the figures.

The signaling flow and operation involved in trajectory control forouter and backhaul moving cells will now be described. FIG. 11 showsexemplary message sequence chart 1100 according to some aspects. Asshown in FIG. 11 , outer moving cells 702-706, backhaul moving cells 708and 710, and central trajectory controller 714 may be involved in thetrajectory control for outer and backhaul moving cells. Centraltrajectory controller 714 may first perform initialization and setupwith backhaul moving cells 708 and 710 and outer moving cells 702-706 instages 1102 and 1104, respectively. For example, in stage 1102, cellinterface 1002 of central trajectory controller 714 may exchangesignaling (according to a predefined initialization and setup procedure)with the central interfaces 914 of backhaul moving cells 708 and 710.Cell interface 1002 may therefore may establish signaling connectionswith backhaul moving cells 708 and 710. Likewise, in stage 1104, cellinterface 1002 of central trajectory controller 714 may exchangesignaling (according to a predefined initialization and setup procedure)with the central interfaces 814 of outer moving cells 702-706, and maytherefore establish signaling connections with backhaul moving cells702-706. As previously discussed regarding FIG. 7 , central trajectorycontroller 714 may interface with network access node 712 (e.g., as partof network access node 712, as an edge computing component, as part ofthe core network behind network access node 712, or from an externalnetwork location), and may exchange this signaling with centralinterfaces 814 and 914 over data bearers that use the radio accessnetwork provided by network access node 712. Further references tocommunication between cell interface 1002 and central interfaces 814 and914 are understood as referring to data exchange over such data bearers.

In addition to establishing signaling connections with outer movingcells 702-706 and backhaul moving cells 708 and 710 in stages 1102 and1104, central trajectory controller 714 may also obtain input data forcomputing coarse trajectories and initial routings as part of theinitialization and setup with outer moving cells 702-706 and backhaulmoving cells 708 and 710. For example, as part of stages 1102 and 1104,central interfaces 814 and 914 may send input data including data raterequirements (e.g., for sending sensing data or access data from servedterminal devices) of outer moving cells 702-706, the positions (e.g.,geographical locations) of outer moving cells 702-706 and backhaulmoving cells 708 and 710, the target areas assigned to outer movingcells 702-706 (e.g., for sensing or access), recent radio measurementsobtained by outer moving cells 702-706 and backhaul moving cells 708-710(e.g., obtained by their respective baseband subsystems 806 and 906),and/or details about the radio capabilities of outer moving cells702-706 and backhaul moving cells 708-710 (e.g., transmit powercapabilities, effective operation range, etc.). Cell interface 1002 ofcentral trajectory controller 714 may receive this input data andprovide it to input data repository 1004, which may store the input datafor subsequent use by trajectory processor 1006. In some aspects, cellinterface 1002 may also be configured to communicate with network accessnode 712, and may, for example, receive input data such as radiomeasurements by network access node 712 (e.g., of signals transmitted byouter moving cells 702-706 and backhaul moving cells 708-710).

Central trajectory controller 714 may be configured to use this inputdata for the central trajectory algorithm executed by trajectoryprocessor 1006. In some aspects, the central trajectory algorithm mayalso use, as input data, a statistical model of the radio environmentbetween outer moving cells 702-706, backhaul moving cells 708 and 710,and the radio access network (e.g., network access node 712 optionallyin addition to one or more additional network access nodes). Variousaspects of this disclosure may use statistical models of varyingcomplexity. For example, in some aspects the statistical model can be abasic propagation model (e.g., a free-space pathloss model) thatevaluates the distance between devices and their current radioconditions to estimate the channel conditions between the devices (e.g.,that models the radio environment based on the distance between devicesand their current radio conditions). In other aspects, the statisticalmodel can be based on a radio map (e.g., a radio environment map (REM))that indicates channel conditions over a mapped area. This type ofstatistical model can therefore use more advanced geographic data tomodel the radio environment over geographic areas having differentpropagation characteristics.

FIG. 12 shows a basic example illustrating the concept of a radio mapaccording to some aspects. Radio map 1200 shown in FIG. 12 assigns achannel condition rating to each of a plurality of geographic units,where lighter-shaded geographic units indicate better channel conditions(estimated) than darker-shaded geographic units. The shades of thegeographic units can indicate, for example, estimated pathloss of radiosignals traveling through the geographic unit, where each shade can beassigned a specific pathloss value (e.g., in dBs or a similar metric).The configuration of radio map 1200 is exemplary. Accordingly, otherradio maps using uniform and non-uniform grids with different types ofgeographic unit shapes and sizes can likewise be used withoutlimitation. While radio map 1200 depicts a single radio parameter (asindicated by the shading of the geographic units), this is alsoexemplary, and radio maps can be applied that assign multiple radioparameters to the geographic units.

Input data repository 1004 may store the underlying radio map data forsuch a radio map. In some aspects, input data repository 1004 maydownload part or all of this radio map data from a remote location, suchas a remote server that stores radio map data (e.g., a REM server). Insome aspects, input data repository 1004 may generate part or all of theradio map data locally (e.g., based on the input data provided by outermoving cells 702-706, backhaul moving cells 708 and 710, and the radioaccess network).

In some aspects, input data repository 1004 may update the radio mapdata based on the input data provided in stages 1102 and 1104 by outermoving cells 702-706, backhaul moving cells 708 and 710, and the radioaccess network. For example, input data repository 1004 may beconfigured to match radio measurements (of the input data) with thecorresponding positions of the device that made the measurement. Inputdata repository 1004 may then update the radio parameters in thegeographic unit of the radio map in which the position is located basedon the radio measurement. This type of updating may therefore adapt theradio map data based on measurements provided by devices in the radioenvironment.

The input data obtained by input data repository 1004 can thereforeinclude the input data provided by outer moving cells 702-706 andbackhaul moving cells 708 and 710 as well as other input data related tothe statistical model of the radio environment (e.g., for basicpropagation models or radio map data). After obtaining this input data,central trajectory controller 714 may compute the coarse trajectoriesand initial routings for outer moving cells 702-706 and backhaul movingcells 708 and 710 in stage 1106. For example, input data repository 1004may provide the input data to trajectory processor 1006, which may thenexecute the central trajectory algorithm using the input data as input.

As previously indicated, the outputs of the central trajectory algorithmmay be coarse trajectories (e.g., static positions, sequences of staticpositions, or paths or contours) that central trajectory controller 714assigns to outer moving cells 702-706 and backhaul moving cells 708 and710. The outputs can also include initial routings that govern the flowof data between outer moving cells 702-706, backhaul moving cells 708and 710, and the radio access network. In some aspects, the centraltrajectory algorithm may be configured to compute these coarsetrajectories and initial routings to optimize an optimization criteriaaccording to the statistical model. As previously indicated, thestatistical model may provide a probabilistic characterization of theradio environment between outer moving cells 702-706, backhaul movingcells 708 and 710, and the radio access network. Accordingly, thecentral trajectory algorithm may evaluate the statistical model toestimate the radio environment over a range of possible coarsetrajectories and/or routings, and may determine coarse trajectoriesand/or initial routings that optimize an optimization criteria relatedto the radio environment.

For example, in some aspects the optimization criteria may be asupported data rate. In this example, outer moving cells 702-706 mayhave minimum data rate requirements. Outer moving cells 702-706 may begenerating uplink data related to sensing (e.g., sensing data generatedby outer moving cells 702-706) or related to access (e.g., uplink datagenerated by the terminal devices served by outer moving cells 702-706),and this uplink data may have a certain minimum data rate that iscapable of supporting transmission of this sensing data. If the backhaulrelaying path (including a fronthaul link from outer moving cell tobackhaul moving cell, and a backhaul link from backhaul moving cell tonetwork access node) has a data rate that is at least this minimum datarate, the uplink data may be successfully transmitted to the network.

Accordingly, the central trajectory algorithm may determine coarsetrajectories and initial routings in stage 1106 that increase ormaximize a function of the supported data rate using the statisticalmodel to approximate the data rate. This can use any type of suitableoptimization algorithm, such as gradient descent (used herein tocollectively refer to both gradient descent and ascent) or anotheroptimization algorithm that incrementally ‘steps’ over differentpossible coarse trajectories and/or initial routings to find a coarsetrajectory or initial routing that increases or maximizes the supporteddata rate. In some aspects, the central trajectory algorithm mayincrease or maximize the overall supported data rate of each backhaulrelaying path outgoing from outer moving cells 702-706 (e.g., anaggregate across all backhaul relaying paths from outer moving cells702-706 to the radio access network). In other aspects the centraltrajectory algorithm may increase or maximize the probability that eachbackhaul relaying path outgoing from outer moving cells 702-706 has asupported data rate above a predefined data rate threshold.

Additionally or alternatively, in some aspects the optimization criteriamay be a link quality metric. The link quality metric can be signalstrength, signal quality, signal-to-noise ratio (SNR or another relatedmetric such as signal-to-interference-plus-noise ratio (SINR)), errorrate (e.g., bit error rate (BER), block error rate (BLER), packet errorrate (PER), or any other type of error rate), distance betweencommunication devices, estimated pathloss between communication devices,or any other type of link quality metric. The central trajectoryalgorithm can similarly be configured to determine coarse trajectoriesand/or initial routings for outer moving cells 702-706 and backhaulmoving cells 708 and 710 by optimizing a link quality metric as theoptimization criteria. For example, the central trajectory algorithm canincrease or maximize a function of the link quality metric using thestatistical model to approximate the link quality metric. As in the caseabove, the function can be a function of the link quality metric itself(e.g., an aggregate over the backhaul relaying paths) or a function ofthe probability that the link quality metric is above a link qualitymetric threshold (e.g. a probability that each backhaul relaying pathhas a link quality metric above the link quality metric threshold).

Although the above examples identify individual optimization criteria,in some aspects the central trajectory algorithm may be configured toevaluate multiple optimization criteria simultaneously. For example, aweighted combination of the individual functions of the optimizationcriteria can be defined and subsequently used as the function to beincreased or maximized with the optimization algorithm.

As the backhaul relaying paths from each outer moving cell includes botha fronthaul link (to a backhaul moving cell) and a backhaul link (fromthe backhaul moving cell to the network), the coarse trajectories mayattempt to balance between strong fronthaul links 716-720 and strongbackhaul links 722-724. For example, if the central trajectory algorithmdetermines coarse trajectories that place backhaul moving cells 708 and710 very close to outer moving cells 702-706, this may yield strongfronthaul links 716-720. However, this may position backhaul movingcells 708 and 710 further from network access node 712, which may yieldweaker backhaul links 722-724. The supported data rate and/or linkquality metric of the backhaul relaying paths may therefore not be ashigh as if the central trajectory algorithm determines coarsetrajectories that place backhaul moving cells 708 and 710 in the middlebetween outer moving cells 702-706 and network access node 712. As thecentral trajectory algorithm models the supported data rate and/or linkquality metric with an optimization criteria, increasing or maximizingthe function of the optimization criteria may yield coarse trajectoriesthat appropriately place backhaul moving cells 708 and 710 between outermoving cells 702-706 and network access node 712.

As indicated above, the central trajectory algorithm may be configuredto use the statistical model of the radio environment to approximate thefunction of the optimization criteria. For example, in cases where thestatistical model is a basic propagation model, the central trajectoryalgorithm may be configured to approximate the optimization criteriausing the basic propagation model, such as by using a supported datarate function that takes into consideration the relative distancesbetween outer moving cells 702-706, backhaul moving cells 708 and 710,and the radio access network (where, for example, closer relativepositions may yield higher supported data rates than far relativepositions). The central trajectory algorithm may then attempt to findtrajectories for outer moving cells 702-706 and backhaul moving cells708 and 710 that increase this supported data rate function (e.g.,according to gradient descent or another optimization algorithm). Asthere are multiple moving cells, this may include determining individualtrajectories outer moving cells 702-706 and backhaul moving cells 708and 710, where the individual trajectories (when executed together)increase the supported data rate function.

In cases where the statistical model is based on radio map data, thecentral trajectory algorithm may be configured to approximate theoptimization criteria using a propagation model that also depends on theradio parameters for the geographic units of the radio map. Thesupported data rate function can therefore take into consideration therelative distances between outer moving cells 702-706, backhaul movingcells 708 and 710, and the radio access network as well as the radioparameters of the geographic units of the radio map that fall betweentheir respective positions. The central trajectory algorithm can thenlikewise attempt to find trajectories for outer moving cells 702-706 andbackhaul moving cells 708 and 710 that increase or maximize thissupported data rate function. As indicated above, this can includedetermining individual trajectories for outer moving cells 702-706 andbackhaul moving cells 708 and 710 that when executed together increaseor maximize the supported data rate function.

In some aspects, the function of the optimization criteria may alsodepend on the routing, where some routings may yield higher approximatedoptimization criteria than others. For example, with reference to theexemplary context of FIG. 7 , outer moving cell 702 may be able toachieve a higher supported data rate for its uplink data when usingbackhaul moving cell 708 for backhaul than compared to backhaul movingcell 710. Additionally or alternatively, backhaul moving cells 708 and710 may be able to provide backhaul relaying paths with higher supporteddata rates when they relay the uplink data to a particular networkaccess node of the radio access network. As part of stage 1106, thecentral trajectory algorithm may therefore also treat the routings asadjustable parameters that can be used to increase the function of theoptimization criteria. The central trajectory algorithm can thereforedetermine initial routings in stage 1106, which can include selectingwhich of backhaul moving cells 708 and 710 for forward moving cells702-706 to transmit their uplink data to and/or selecting which networkaccess node for backhaul moving cells 708 and 710 to relay this uplinkdata to.

In some aspects, the central trajectory algorithm may also considerconstraint parameters when determining the coarse trajectories andinitial routings. For example, target areas assigned to outer movingcells 702-706 may act as constraints, where outer moving cells 702-706are expected to perform their assigned outer tasks (sensing or routing)in certain target areas. Accordingly, in some cases the coarsetrajectories assigned to outer moving cells 702-706 may be constrainedto being within or near the target areas (e.g., to be proximate enoughto the target area to perform the assigned outer task with outer tasksubsystem 820). When attempting to increase the function of theoptimization criteria, the central trajectory algorithm may thereforeconsider, and in some aspects consider exclusively, coarse trajectoriesof outer moving cells 702-706 that are constrained by their respectivelyassigned target areas. In some aspects, backhaul moving cells 708 and710 may also have geographical constraints that the central trajectoryalgorithm may consider when determining the coarse trajectories.

In some aspects, the central trajectory algorithm may determine thetarget areas for outer moving cells 702-706 as part of the coarsetrajectory determination. For example, the central trajectory algorithmmay identify an overall target area (e.g., as reported by outer movingcells 702-706 as input data) that defines the overall geographic area inwhich the outer moving cells 702-706 are assigned to perform their outertasks. Instead of treating the target area of each outer moving cell asthe area to which each individual outer moving cell is assigned to, thecentral trajectory algorithm may determine coarse trajectories for outermoving cells that increase the optimization criteria while also coveringthe overall target area.

After determining the coarse trajectories and initial routings in stage1106, central trajectory controller 714 may send the coarse trajectoriesand initial routings to backhaul moving cells 708 and 710 and outermoving cells 702-706 in stages 1108 and 1110, respectively. For example,trajectory processor 1006 may provide the coarse trajectories andinitial routings to cell interface 1002, which may then send the coarsetrajectories and initial routings to its peer central interfaces 814 and914 at outer moving cells 702-706 and backhaul moving cells 708 and 710.In some aspects, cell interface 1002 may identify the coarse trajectoryand initial routing individually assigned to each of outer moving cells702-706 and backhaul moving cells 708 and 710, and may then transmit thecoarse trajectory and initial routing to each moving cell to thecorresponding central interface 814 or 914 of the moving cells.

Backhaul moving cells 708 and 710 and outer moving cells 702-706 maythen receive the coarse trajectories and initial routings at centralinterfaces 814 and 914, respectively. As shown in FIG. 11 , backhaulmoving cells 708 and 710 may then establish connectivity with outermoving cells 702-706 in stage 1112. For example, backhaul moving cells708 and 710 may set up a backhaul relaying path with outer moving cells702-706 that outer moving cells 702-706 can use to transmit and receivedata with the radio access network (including network access node 712).This can include, for example, setting up fronthaul links 716-720between outer moving cells 702-706 and backhaul moving cells 708 and 710and setting up backhaul links 722 and 724 between backhaul moving cells708 and 710 and the radio access network (although in some aspects thebackhaul links may already be established). In some aspects, backhaulmoving cells 708 and 710 may also set up a link with each other, withwhich they can, for example, coordinate their updated trajectories.

In some aspects, backhaul moving cells 708 and 710 and outer movingcells 702-706 may execute stage 1112 at their cell interfaces 816 and916. For example, with reference to outer moving cell 702, its centralinterface 814 may receive the coarse trajectory and initial routingassigned to outer moving cell 702 in stage 1110. Central interface 814of outer moving cell 702 may then provide the coarse trajectory totrajectory processor 818 and the initial routing to cell interface 816.The initial routing may specify that outer moving cell 702 is assignedto use one of backhaul moving cells 708 and 710, such as backhaul movingcell 708. Accordingly, cell interface 816 of outer moving cell 702 mayidentify that it is assigned to establish a backhaul relaying path tothe radio access network via backhaul moving cell 708. Cell interface816 of outer moving cell 702 may therefore establish connectivity withcell interface 916 of backhaul moving cell 708, such as by exchangingwireless signaling (via baseband subsystem 806 of outer moving cell 702and baseband subsystem 906 of backhaul moving cell 708) with each otherthat establishes a fronthaul link between outer moving cell 702 andbackhaul moving cell 708. Outer moving cells 702-706 may similarlyestablish connectivity with the backhaul moving cells assigned to themby their respective initial routings.

In some aspects, the central trajectory algorithm may determine coarsetrajectories but not initial routings. Accordingly, outer moving cells702-706 and backhaul moving cells 708 and 710 may be configured todetermine the routings (e.g., to determine backhaul relaying paths). Forexample, the cell interfaces 814 of outer moving cells 702-706 mayperform a discovery process to identify nearby backhaul moving cells,and may then select a backhaul moving cell to use as a backhaul relayingpath. These routings may therefore be the initial routings. Outer movingcells 702-706 and backhaul moving cells 708 and 710 may then establishconnectivity with each other according to these initial routings.

After establishing connectivity, outer moving cells 702-706 may performtheir outer tasks while moving according to their respectively assignedcoarse trajectories in stage 1114. For example, with exemplary referenceto outer moving cell 702, trajectory processor 818 may provide thecoarse trajectory to movement controller 824. Movement controller 824may then provide control signals to steering and movement machinery 826that direct steering and movement machinery 826 to move outer movingcell 702 according to its coarse trajectory. If configured to performsensing as its outer task, one or more sensors (not explicitly shown inFIG. 8 ) of outer task subsystem 820 may obtain sensing data. Ifconfigured to perform access as its outer task, outer task subsystem 820may use baseband subsystem 806 to wirelessly provide radio access toterminal devices in the coverage area of outer moving cell 702.

As previously indicated, the coarse trajectories may be staticpositions, sequences of static positions, or a paths or contours. If thecoarse trajectory is a static position, movement controller 824 maycontrol steering and movement machinery 826 to position outer movingcell 702 at the static position and to remain at the static position. Ifthe coarse trajectory is a sequence of static positions, movementcontroller 824 may control steering and movement machinery 826 tosequentially move outer moving cell 702 to each of the sequence ofstatic positions. The sequence of static positions can be time-stamped,and movement controller 824 may control steering and movement machinery826 to move outer moving cell 702 to each of the sequence of staticpositions at the according to the time stamps. If the coarse trajectoryis a path or contour, movement controller 824 may control steering andmovement machinery 826 to move outer moving cell 702 along the path orcontour.

As shown in FIG. 11 , outer moving cells 702-706 and backhaul movingcells 708 and 710 may perform data transmission in stages 1116 and 1118.For example, outer moving cells 702-706 (e.g., at their respective cellinterfaces 816) may transmit uplink data from the outer task on theirrespective fronthaul links 716-720 to backhaul moving cells 708 and 710as assigned by the initial routings. Backhaul moving cells 708 and 710may then receive the uplink data at their respective cell interfaces916. Relay routers 920 may then identify the uplink data received at thecell interfaces 916 and transmit the uplink data to the radio accessnetwork on respective backhaul links 722 and 724 via the basebandsubsystems 906. In some aspects, fronthaul moving cells 702-706 may alsouse the backhaul relaying paths for downlink data transmission.Accordingly, backhaul moving cells 708 and 710 may receive downlink dataaddressed to outer moving cells 702-706 from the radio access network attheir baseband subsystems 906. Relay routers 920 may identify thisdownlink data and provide it to the cell interfaces 916, which may thentransmit the downlink data (via baseband subsystem 906) on the fronthaullink to outer moving cells 702-706.

Similar to outer moving cells 702-706, backhaul moving cells 708 and 710may move according to their assigned coarse trajectories during stages1116 and 1118. Accordingly, with exemplary reference to backhaul movingcell 708, trajectory processor 918 (after receiving the coarsetrajectory from central interface 914) may specify the coarse trajectoryto movement controller 924. Movement controller 924 may then directsteering and movement machinery 926 to move backhaul moving cell 708according to the coarse trajectory.

These coarse trajectories and initial routings determined by centraltrajectory controller 714 can be considered a high-level plan that formsthe initial basis of the trajectories and routing of outer moving cells702-706 and backhaul moving cells 708 and 710. Accordingly, in someaspects outer moving cells 702-706 and backhaul moving cells 708 and 710may perform local optimization of the trajectories and routing. As shownin FIG. 11 , outer moving cells 702-706 and backhaul moving cells 708and 710 may perform parameter exchange in stage 1120, such as by usingtheir cell interfaces 816 and 816 to exchange parameters over thesignaling connections. These parameters may be related to the localinput data used as input by trajectory processors 818 and 918 of outermoving cells 702-706 and backhaul moving cells 708 and 710 for theirouter and backhaul trajectory algorithms, respectively. For example, theparameters can include similar information to the input data, such asdata rate requirements of the moving cells, the positions of the movingcells, the target areas assigned to the moving cells, recent radiomeasurements obtained by the moving cells, and/or details about theradio capabilities of the moving cells. The parameters can also includethe coarse trajectories assigned to the moving cells by the centraltrajectory algorithm. In some aspects, outer moving cells 702-706 andbackhaul moving cells 708 and 710 may also receive parameters from otherlocations, such as from the radio access network (e.g., network accessnode 712). In some aspects, backhaul moving cells 708 and 710 mayexchange parameters directly with each other.

After obtaining the parameters, cell interfaces 816 and 916 may providethe parameters to trajectory processors 818 and 918. With exemplaryreference to trajectory processor 818 of outer moving cell 702,trajectory processor 818 may use the parameters as local input data forthe outer trajectory algorithm. In some aspects, trajectory processor818 may also use other information as the local input data, such asradio measurements performed by baseband subsystem 806 as well as itscurrent coarse trajectory assigned by central trajectory controller 714.Trajectory processor 818 may then perform local optimization of itstrajectory and routing in stage 1122 by executing the outer trajectoryalgorithm in stage 1122. Likewise, with exemplary reference totrajectory processor 918 of backhaul moving cell 708, trajectoryprocessor 918 may use the parameters as local input data for thebackhaul trajectory algorithm. Trajectory processor 918 may then performlocal optimization of its trajectory and routing by executing thebackhaul trajectory algorithm in stage 1122.

The outer and backhaul trajectory algorithms executed by outer movingcells 702-706 and backhaul moving cells 708 and 710 may be similar tothe central trajectory algorithm executed by central trajectorycontroller 714. For example, in some aspects, the outer and backhaultrajectory algorithms may also function by determining trajectoriesand/or routings that increase or otherwise maximize an optimizationcriteria. In some aspects, the optimization criteria used by the outerand backhaul trajectory algorithms may be the same as the optimizationcriteria used by the central trajectory algorithm. In some aspects, theouter and backhaul trajectory algorithms may similarly use a statisticalmodel of the radio environment to approximate the optimization criteria,such as a basic propagation model or a propagation model based on aradio map.

For example, in some aspects, the outer and backhaul trajectoryalgorithms may determine an updated trajectory and/or updated routingfor the moving cell executing the trajectory algorithm that increasesthe optimization criteria (e.g., by incrementally stepping parameters toguide a function of the optimization criteria toward a maximum value).Accordingly, in comparison to the central trajectory algorithm, whichconcurrently determines coarse trajectories and/or initial routings formultiple moving cells, the outer and backhaul trajectory algorithms mayseparately focus on the individual moving cell executing the trajectoryalgorithm. For example, trajectory processor 918 of backhaul moving cell708 may attempt to determine an updated trajectory for backhaul movingcell 708 that increases or maximizes the function of the optimizationcriteria based on the position of backhaul moving cell 708. As thefunction of the optimization criteria (e.g., supported data rate and/orlink quality metric of the backhaul relaying paths) depends on bothfronthaul links 716-720 and backhaul links 722 and 724, trajectoryprocessor 918 may determine an updated trajectory that yields an optimalbalance between fronthaul and backhaul links (and thus increases ormaximizes the function of the optimization criteria).

In some aspects, trajectory processors 818 and 918 of the moving cellsmay execute stage 1122 in an alternating manner. For example,dual-phased optimization can be used, where outer moving cells 702-706and backhaul moving cells 708 and 710 may alternate between optimizingthe trajectories of outer moving cells 702-706 and the trajectories ofbackhaul moving cells 708-710. In this example, the trajectoryprocessors 818 of outer moving cells 702-706 may be configured toexecute the outer trajectory algorithm using their current trajectory(e.g., the coarse trajectory), current routing, and relevant parametersfrom stage 1120 as the local input data for the outer trajectoryalgorithm. The outer trajectory algorithm may be configured to, usingthis local input data, determine an update to its current trajectorythat steps the function of the optimization criteria toward a maximumvalue (e.g., by some incremental step). As described for the centraltrajectory algorithm, this can be done using gradient descent or anotheroptimization algorithm. The outer trajectory algorithm can alsodetermine an updated routing (e.g., if the updated trajectory would leadto a better routing for the optimization criteria).

Accordingly, each of outer moving cells 702-706 may determine arespective updated trajectory and/or updated routing. Then, outer movingcells 702-706 may perform another round of parameter exchange by sendingthe updated trajectories and/or routing to backhaul moving cells 708 and710. Backhaul moving cells 708 and 710 may then use these updatedtrajectories and/or routing, in addition to any other relevantparameters, as local input data for the backhaul trajectory algorithm.Trajectory processors 916 of backhaul moving cells 708 and 710 maytherefore execute the backhaul trajectory algorithm using this localinput data to determine updated trajectories for backhaul moving cells708 and 710. For example, as the trajectories of outer moving cells702-706 have changed to the updated trajectories, the backhaultrajectory algorithm may be configured to determine updated trajectoriesfor backhaul moving cells 708 and 710 that increase (e.g., maximize) theoptimization criteria given the updated trajectories of outer movingcells 702-706. The backhaul trajectory algorithm may also be configuredto change the routings, e.g., to change the updated routings determinedby outer moving cells 702-710 to new updated routings that optimize theupdated trajectories of backhaul moving cells 708 and 710.

After backhaul moving cells 708 and 710 have determined their ownupdated trajectories and/or updated routings, backhaul moving cells 708and 710 may perform another round of parameter exchange and send theirupdated trajectories and/or updated routings to outer moving cells702-706. Outer moving cells 702-706 may then again execute the outertrajectory algorithm using these updated trajectories and/or updatedroutings from backhaul moving cells 708 and 710 to determine new updatedtrajectories and/or routings that increase the optimization criteria.This dual-phased optimization may continue to repeat over time. In someaspects, an aggregate metric across both outer and backhaul can be usedto steer the trajectories away from diverging in one direction. In someaspects, central trajectory controller 714 may periodically re-executethe central trajectory algorithm and provide new coarse trajectoriesand/or new initial routings to outer moving cells 702-706 and backhaulmoving cells 708 and 710. This can be viewed as a type of periodicreorganization, where central trajectory controller 714 periodicallyreorganizes outer moving cells 702-706 and backhaul moving cells 708 and710 in a centralized manner.

The local optimization is not limited to such dual-phased optimizationapproaches. In some aspects, outer moving cells 702-706 and backhaulmoving cells 708 and 710 may execute their trajectory algorithms toupdate their trajectories and/or routing in an alternating orround-robin fashion, e.g., one of outer moving cells 702-706 andbackhaul moving cells 708 and 710 at a time or other appropriatecoordination implementation. In some aspects, one of outer moving cells702-706, referred to here as a master outer moving cell, may assume theresponsibility of determining updated trajectories and/or routing forone or more (or all) of the rest of outer moving cells 702-706.Accordingly, similarly to the central trajectory algorithm thatconcurrently evaluated trajectories for multiple outer moving cells, themaster outer moving cell may execute an outer trajectory algorithm thatconcurrently determines updated trajectories and/or updated routings formultiple outer moving cells (e.g., by determining updated trajectoriesthat maximize the optimization criteria). The master outer moving cellmay then transmit the updated trajectories and/or routings to the otherouter moving cells, which may then move according to the updatedtrajectories. This can similarly be applied for backhaul moving cells,where one of backhaul moving cells 708 or 710 may assume the role ofmaster backhaul moving cell and determine updated trajectories and/orupdated routings for multiple (or all) backhaul moving cells.

In some cases, the use of local optimization may lead to betterperformance. For example, as previously indicated outer moving cells702-706 and backhaul moving cells 708 and 710 may be configured toexchange parameters prior to and between rounds of local optimization.These parameters can include current radio measurements, which can bemore accurate indicators of the radio environment than the basicpropagation model and/or radio maps used by central trajectorycontroller 714. Accordingly, in some cases, the local optimization maybe based on a more accurate reflection of the actual radio environment,and may therefore lead to better optimization criteria (e.g., bettervalues of the metric being used as the optimization criteria) inpractice.

Furthermore, in some aspects the use of local optimization may result ina more advantageous division of processing. For example, outer movingcells 702-706 and backhaul moving cells 708 and 710 may not be able tosupport the same processing power as a server-type component such ascentral trajectory controller 714. Accordingly, depending on theirdesign constraints, it may not be feasible for outer moving cells702-706 and backhaul moving cells 708 and 710 to execute a fulltrajectory algorithm to locally determine their trajectories fromscratch. The use of local optimization may enable central trajectorycontroller 714 to determine a high-level plan for trajectories whilealso allowing outer moving cells 702-706 and backhaul moving cells 708and 710 to make local adjustments as needed (e.g., that are onlyadjustments as compared to determining new trajectories from the start).

Additionally, in some cases outer moving cells 702-706 and backhaulmoving cells 708 and 710 may be able to adjust their trajectories with alower latency than would occur if central trajectory controller 714 hadfull control over their trajectories (e.g., without any localoptimization). For example, outer moving cells 702-706 and backhaulmoving cells 708 and 710 can be configured to make local adjustments totheir trajectories (e.g., based on their radio measurements and otherparameter exchange) without having to first send data back to centraltrajectory controller 714 and subsequently waiting to receive aresponse.

In the exemplary context of FIG. 11 , the central trajectory algorithmmay exert positioning control over both outer moving cells 702-706 andbackhaul moving cells 708 and 710. As previously indicated, otheraspects of this disclosure are also directed to cases where centraltrajectory controller 714 exerts control over backhaul moving cells 708and 710 but not outer moving cells 702-706. Other cases, for example,where backhaul moving cells 708 and 710 are present without any outermoving cells are also applicable. FIG. 13 shows one such exampleaccording to some aspects, where backhaul moving cells 708 and 710 mayprovide backhaul to various terminal devices and/or outer moving cells734 and 736 (e.g., that are not controllable by central trajectorycontroller 714).

In these exemplary cases, central trajectory controller 714 may be ableto provide coarse trajectories and/or routing to backhaul moving cells708 and 710, but not to any of the served devices 734 and 736 (e.g.,outer moving cells and/or terminal devices) as they may not be under thepositional control of central trajectory controller 714. FIG. 14 showsexemplary message sequence chart 1400 according to some aspects, whichrelates to these cases. As shown in FIG. 14 , central trajectorycontroller 714 and backhaul moving cells 708 and 710 may first performinitialization and setup in stage 1402 (e.g., in the same or similarmanner as stage 1102). Central trajectory controller 714 may thencompute coarse trajectories and initial routing using the input data andcentral trajectory algorithm in stage 1404.

As central trajectory controller 714 is only providing coarsetrajectories for backhaul moving cells 708 and 810 in these aspects, thecentral trajectory algorithm may be different. For example, in theprevious context of FIG. 11 , central trajectory controller 714 couldevaluate the optimization criteria using specific positions of outermoving cells 702-706 (e.g., approximate the supported data rate or linkquality metric given specific locations of outer moving cells 702-706using the statistical model of the radio environment). However, in thecontext of FIG. 14 , the central trajectory algorithm may not be able toassume specific positions of the served devices, and may instead usestatistical estimations of their positions.

For example, in some aspects, the central trajectory algorithm may usethe concept of a virtual node to statistically estimate the position ofserved devices 734-736. For example, in some aspects input datarepository 1004 of central trajectory controller 714 may be configuredto collect statistical density information about served devices 734-736.In some cases, the statistical density information can be statisticalgeographic density information, such as basic information such as thereported positions of served devices 734-736 and/or more complexinformation such as a heat map indicating a density of served devices734-736 over time. In some cases, the statistical density informationcan additionally or alternatively include statistical traffic densityinformation, which indicates the geographic density of data traffic. Forexample, if there are only a few served devices in a given area butthese served devices are generating considerable data traffic, thestatistical traffic density information can indicate the increased datatraffic in this area (whereas strictly geographic density informationwould indicate only that there are a few served devices). Thisstatistical density information can be reported to central trajectorycontroller 714 by backhaul moving cells 708 and 710 (e.g., based ontheir own radio measurements or position reporting), from the radioaccess network, and/or from external network locations.

Accordingly, when executing the central trajectory algorithm in stage1404, trajectory processor 1006 may use this statistical densityinformation as input data. In some aspects, the central trajectoryalgorithm may utilize a similar optimization algorithm as describedabove for stage 1106. For example, this can include applying gradientdescent (or another optimization algorithm) to determine coarsetrajectories and/or routing for backhaul moving cells 708 and 710 thatincrease or maximize an optimization criteria, where the optimizationcriteria is represented by a function based on the statistical model ofthe radio environment. However, in contrast to the case of FIG. 11 , thecentral trajectory algorithm may not have specific locations of serveddevices 734-736, and may instead use the statistical density informationto characterize virtual served devices. For example, the centraltrajectory algorithm can approximate the positions of the virtual serveddevices using the statistical density information (e.g., the expectedposition of virtual served devices), and then use these positions whendetermining coarse trajectories and/or initial routings for backhaulmoving cells 708 and 710. As served devices 734-736 are not under thepositional control of central trajectory controller 714, the centraltrajectory algorithm may only determine coarse trajectories and/orinitial routing for backhaul moving cells 708 and 710 (where the initialroutings assign backhaul moving cells 708 and 710 to provide backhaulfor certain of served devices 734-736). Similar to the case of FIG. 11 ,the optimization criteria can be, for example, supported data rateand/or link quality metric (including aggregate values and probabilitiesthat the optimization criteria is above a predefined threshold for eachbackhaul relaying path).

As shown in FIG. 13 , the backhaul relaying paths (on which theoptimization criteria are based) may include a fronthaul link and abackhaul link. For example, backhaul moving cell 708 may have fronthaullinks 726 with its served devices 734 and backhaul link 730 with networkaccess node 712 while backhaul moving cell 708 may have fronthaul links728 with its served devices 736 and backhaul link 732 with networkaccess node 712. As the function of the optimization criteria depends onboth fronthaul and backhaul links, the coarse trajectories determined bycentral trajectory controller 714 for backhaul moving cells 708 and 710may therefore position backhaul moving cells 708 and 710 to jointlyoptimize fronthaul links 726-728 and backhaul links 730-732 (e.g., toyield fronthaul and backhaul links that increase or maximize thefunction of the optimization criteria). The coarse trajectories maytherefore jointly balance between strong fronthaul and strong backhaullinks.

After determining the coarse trajectories and/or initial routing instage 1404, central trajectory controller 714 may send the coarsetrajectories and/or initial routings to backhaul moving cells 708 and710 (e.g., using signaling connections between cell interface 1002 ofcentral trajectory controller 714 and its peer central interfaces 914 ofbackhaul moving cells 708 and 710). Backhaul moving cells 708 and 710may then establish connectivity with served devices 734-736 in stage1408 (e.g., using the initial routing provided by central trajectorycontroller 714, or by determining their own initial routings). If any ofserved devices 734-736 are outer moving cells, these served devices mayperform an outer task in stage 1410. Served devices 734-736 may thentransmit uplink data to backhaul moving cells 708 and 710 usingfronthaul links 726-728 in stage 1412, and backhaul moving cells 708 and710 may transmit the uplink data to the radio access network in stage1414 on backhaul links 730 and 732. Stages 1412 and 1414 can alsoinclude transmission and relaying of downlink data from the radio accessnetwork to served devices 734-736 via the backhaul relaying pathprovided by backhaul moving cells 708 and 710. Backhaul moving cells 708and 710 may move according to their respectively assigned coarsetrajectories during stages 1412 and 1414.

Similar to the case of FIG. 11 , the coarse trajectories and/or initialroutings provided by central trajectory controller 714 may form ahigh-level plan that can be locally optimized. Accordingly, as shown inFIG. 14 , backhaul moving cells 708 and 710 may perform parameterexchange with served devices 734-736 in stage 1416. In some aspects,served devices 734-736 may provide position reports to backhaul movingcells 708 and 710 in stage 1416, which backhaul moving cells can use toupdate the statistical density information of served devices 734-736.This updated statistical density information may be part of the localinput data for the backhaul trajectory algorithm. The parameter exchangethat forms the local input data can include any of data raterequirements of served devices 734-736, the positions of served devices734-736, the target areas assigned to served devices 734-736, recentradio measurements obtained by served devices 734-736, and/or detailsabout the radio capabilities of served devices 734-736.

Backhaul moving cells 708 and 710 may then perform local optimization ofthe trajectories and/or routing in stage 1418 by executing the backhaultrajectory algorithm on the local input data. The backhaul trajectoryalgorithm may calculate updated trajectories and/or updated routingsbased on the local input data. After determining the updatedtrajectories and/or updated routings, backhaul moving cells 708 and 710may move according to the updated trajectories and/or perform backhaulrelaying according to the updated routings. In some aspects, backhaulmoving cells 708 and 710 may repeat stages 1412-1418 over time, and maythus repeatedly execute the backhaul trajectory algorithm using newlocal input data to update the trajectories and/or routings. As thelocal input data may reflect the actual radio environment, in some casesthe local optimization can improve performance.

In some aspects, backhaul moving cells 708 and 710 may use dual-phasedoptimization to alternate between optimizing fronthaul links 726-728 andbackhaul links 730-732. Using backhaul moving cell 708 as an example,trajectory processor 918 may alternate between determining an updatedtrajectory that optimizes fronthaul links 726 (e.g., based on linkstrength, supported data rate, and/or link quality metric) anddetermining an updated trajectory that optimizes backhaul links 730. Byalternating between optimizing fronthaul and backhaul, trajectoryprocessor 918 may optimize the function of the optimization criteria(which can depend on both fronthaul and backhaul links).

Various aspects of this disclosure consider one or more additionalextensions to these systems. In some aspects, one or more of outermoving cells 702-706 and backhaul moving cells 708 and 710 may beconfigured to support multiple simultaneous radio links. Accordingly,instead of only using a single radio link for the fronthaul or backhaullink, one or more of the moving cells may be configured to transmitand/or receive using multiple radio links. In such cases, centraltrajectory controller 714 may have prior knowledge of the multi-linkcapabilities of the moving cells. The central trajectory algorithm maytherefore use channel statistics representing the aggregate capacityacross the multiple links when determining the coarse trajectoriesand/or initial routings. For example, if the data rate of a firstavailable link of a moving cell is R₁ and the data rate of a secondavailable link of the moving cell is R₂, the central trajectoryalgorithm may assume that the data rate of both links together is R₁+R₂(e.g., treated independently, thus making the aggregate capacityadditive). Similarly, if the moving cells support mmWave, the centraltrajectory algorithm can model the multiple beams from mmWave asmultiple isolated links (e.g., by generating multiple antenna beams withmmWave antenna arrays).

In some aspects, the backhaul routing paths may introduce redundancyusing multiple links. For example, outer moving cells 702-706 or theserved devices may use multiple backhaul routing paths (e.g., withdifferent fronthaul links and/or backhaul links), and may transmit thesame data redundantly over the multiple backhaul routing paths. Thiscould be done as packet-level redundancy.

In some aspects, outer moving cells 702-706 and/or backhaul moving cells708 and 710 may use transmission or reception cooperation to improveradio performance. For example, the central trajectory algorithm maydesignate a cluster of outer moving cells or backhaul moving cells tocooperate as a single group, and can then determine coarse trajectoriesfor the cluster to support transmit and/or receive diversity. Thecentral trajectory algorithm can then treat the cluster as a compositenode (e.g., using an effective rate representation). Once the centraltrajectory algorithm determines the coarse trajectory of the cluster,the moving cells in the cluster can use their outer or backhaultrajectory algorithms to adjust their trajectories so that the effectivecentroid location of the cluster remains constant.

In some aspects, the central, outer, and backhaul trajectory algorithmsmay use features described in J. Stephens et. al. “Concurrent control ofmobility and communication in multi-robot system,” (IEEE Transactions onRobotics, October, 2017), J. L. Ny et. al, “Adaptive communicationconstrained deployment of unmanned aerial vehicle,” (IEEE JSAC, 2012),M. Zavlanos et. al. “Network integrity in mobile robotic network,” (IEEETrans. On Automatic Control, 2013), and/or J. Fink et. al., Motionplanning for robust wireless networking,” (IEEE Conf. On Robotics &Automation, 2012).

FIG. 15 shows exemplary method 1500 for managing trajectories for movingcells according to some aspects. As shown in FIG. 15 , method 1500including establishing signaling connections with one or more backhaulmoving cells and with one or more outer moving cells (1502), obtaininginput data related to a radio environment of the one or more outermoving cells and the one or more backhaul moving cells (1504),executing, using the input data as input, a central trajectory algorithmto determine first coarse trajectories for the one or more backhaulmoving cells and second coarse trajectories for the one or more outermoving cells (1506), and sending the first coarse trajectories to theone or more backhaul moving cells and the second coarse trajectories tothe one or more outer moving cells (1508).

FIG. 16 shows exemplary method 1600 for operating an outer moving cellaccording to some aspects. As shown in FIG. 16 , method 1600 includesreceiving a coarse trajectory from a central trajectory controller(1602), performing an outer task according to the coarse trajectory, andsending data from the outer task to a backhaul moving cell for relay toa radio access network (1604), executing an outer trajectory algorithmwith the coarse trajectory as input to determine an updated trajectory(1606), and performing the outer task according to the updatedtrajectory (1608).

FIG. 17 shows exemplary method 1700 for operating a backhaul moving cellaccording to some aspects. As shown in FIG. 17 , method 1700 includesreceiving a coarse trajectory from a central trajectory controller(1702), receiving data from one or more outer moving cells while movingaccording to the coarse trajectory, and relaying the data to a radioaccess network (1704), executing a backhaul trajectory algorithm withthe coarse trajectory as input to determine an updated trajectory(1706), and receiving additional data from the one or more outer movingcells while moving according to the updated trajectory, and relaying theadditional data to the radio access network (1708).

FIG. 18 shows exemplary method 1800 for managing trajectories for movingcells according to some aspects. As shown in FIG. 18 , method 1800includes establishing signaling connections with one or more backhaulmoving cells (1802), obtaining input data related to a radio environmentof the one or more backhaul moving cells and related to statisticaldensity information of one or more served devices (1804), executing,using the input data as input, a central trajectory algorithm todetermine coarse trajectories for the one or more backhaul moving cells(1806), and sending the coarse trajectories to the one or more backhaulmoving cells (1808).

FIG. 19 shows exemplary method 1900 for operating a backhaul moving cellaccording to some aspects. As shown in FIG. 19 , method 1900 includesreceiving a coarse trajectory from a central trajectory controller(1902), receiving data from one or more served devices while movingaccording to the coarse trajectory, and relaying the data to a radioaccess network (1904), executing a backhaul trajectory algorithm withthe coarse trajectory as input to determine an updated trajectory(1906), and receiving additional data from the one or more serveddevices while moving according to the updated trajectory, and relayingthe additional data to the radio access network (1908).

Mobile Access Nodes for Indoor Coverage

Similar techniques and trajectory algorithms can also be applied forindoor coverage use cases. For example, terminal devices may operate inprivate residences and commercial facilities. This can include terminaldevices, such as handheld mobile phones, as well as connectivity-enabledevices like televisions, printers, and appliances. In some cases, theseterminal devices may follow predictable usage patterns within the indoorcoverage areas. Several examples include users that congregate in aliving room are of a private residence in the evening, meeting roomsthat are frequently used during work hours in an office building, publictransit stations that users wait at during commuting hours, or a stadiumwith many users of mobile access nodes.

FIG. 20 shows an exemplary scenario using building 2000 according tosome aspects. In the example of FIG. 20 , building 2000 may be a privateresidence. Users carrying terminal devices may exhibit predictable usagepatterns inside building 2000. For example, the users may frequently bein building 2000 during evening hours and weekends and may leavebuilding 2000 during work and/or school hours. Accordingly, user demandmay be higher in evenings and weekends and lower during work and/orschool hours. Furthermore, in some cases, the users may followpredictable usage patterns in terms of where and when they are locatedin building 2000. For example, the users may frequently congregate indining room 2012 during early morning and early evening hours forbreakfast and dinner. The users may also congregate in living room 2010during late evening hours.

Users in various private and public coverage areas may similarly followusage patterns that are predictable. Accordingly, in some aspects anetwork of mobile access nodes may follow trajectories that are based onthese predictable usage patterns. Instead of positioning themselves in apurely responsive manner, the mobile access nodes may proactivelyposition themselves according to where users are likely to be. In somecases, this type of trajectory control can improve coverage and serviceto users.

As shown in FIG. 20 , mobile access nodes 2004, 2006, and 2008 can bedeployed within building 2000. Mobile access nodes 2004-2008 may beconfigured to provide access to users within this target coverage area,and may therefore position themselves within building 2000 alongtrajectories that can effectively serve the users. Anchor access point2002 may also be deployed within building 2000, and may be configured toprovide control functions for mobile access nodes 2004-2008.

FIG. 21 shows a basic diagram illustrating the functionality of anchoraccess point 2002 and mobile access nodes 2004 and 2006 according tosome aspects. As shown in FIG. 21 , anchor access point 2002 mayinterface with backhaul link 2102. Backhaul link 2102 may provide anchoraccess point 2002 with a connection to a core network, through whichanchor access point 2002 may connect with various external datanetworks. Backhaul link 2102 can be a wired or wireless link.

Anchor access point 2002 may interface with mobile access nodes 2004 and2006 over anchor links 2104 and 2106. Anchor links 2104 and 2106 may bewired or wireless links. Accordingly, mobile access nodes 2004 and 2006may be free to move and maintain anchor links 2104 and 2106 with anchoraccess point 2002.

As previously indicated, mobile access nodes 2004 and 2006 may provideaccess to various served terminal devices (e.g., users). As shown inFIG. 21 , mobile access nodes 2004 and 2006 may interface with theseserved terminal devices over fronthaul links 2108 and 2110. Accordingly,in the downlink direction, mobile access nodes 2004 and 2006 may receivedownlink data addressed to the served terminal devices from anchoraccess point 2002 over anchor links 2104 and 2106. Mobile access nodes2004 and 2006 may then perform any applicable processing on the downlinkdata and subsequently transmit the downlink data to the served terminaldevices, as appropriate, over fronthaul links 2108 and 2110. In theuplink direction, mobile access nodes 2004 and 2006 may receive uplinkdata originating from the served terminal devices over fronthaul links2108 and 2110. Mobile access nodes 2004 and 2006 may then perform anyapplicable processing on the uplink data and then transmit the uplinkdata to anchor access point 2002 over anchor links 2104 and 2106.

As indicated in FIG. 21 , anchor access point 2002 and mobile accessnodes 2004 and 2006 may have certain functionalities related to thetrajectory control. With reference to anchor access point 2002, anchoraccess point 2002 may provide, for example, central learning, centralcontrol, sensor hub, and central communication (the structure of whichis further described below for FIG. 23 ). Mobile access nodes 2004 and2006 may provide, for example, local learning, local control, localsensing, and local communication (the structure of which is furtherdescribed below for FIG. 22 ).

FIGS. 22 and 23 show exemplary internal configurations of mobile accessnodes 2004 and 2006 and anchor access point 2002 according to someaspects. As shown in FIG. 22 , mobile access nodes 2004 and 2006 mayinclude antenna system 2202, radio transceiver 2204, baseband subsystem2206 (including physical layer processor 2208 and protocol controller2210), application platform 2212, and movement system 2224. Antennasystem 2202, radio transceiver 2204, and baseband subsystem 2206 may beconfigured in a similar or same manner as antenna system 302, radiotransceiver 304, and baseband subsystem 306 as shown and described fornetwork access node 110 in FIG. 3 . Antenna system 2202, radiotransceiver 2204, and baseband subsystem 2206 may therefore beconfigured to perform radio communications to and from anchor accesspoint 2002.

As shown in FIG. 22 , application platform 2212 may include anchorinterface 2214, local learning subsystem 2216, local controller 2218,sensor 2220, and relay router 2222. In some aspects, anchor interface2214 may be a processor configured to communicate with a peer mobileinterface of an anchor access point (e.g., mobile interface 2314 asdescribed below for anchor access point 2002). Anchor interface 2214 maytherefore be configured to transmit data to anchor access points byproviding the data to baseband subsystem 2206, which may then processthe data to produce RF signals. RF transceiver 2204 may then wirelesslytransmit the RF signals via antenna system 2202. The anchor access pointmay then receive and process the wireless RF signals to recover the dataat its mobile interface. Anchor interface 2214 may receive data from thepeer mobile interface through the reverse of this process. Anchorinterface 2214 may therefore be configured to communicate with peermobile interfaces of anchor access points over a logical connection thatuses wireless transmission for physical transport. Further references tocommunication between mobile access nodes 2004 and 2006 and anchoraccess point 2002 may involve this type of transmission between anchorinterface 2214 and the peer mobile interface.

Local learning subsystem 2216 may be a processor configured forlearning-based processing. For example, local learning subsystem 2216may be configured to execute program code for a pattern recognitionalgorithm, which can be, for example, an artificial intelligence (AI)algorithm that uses input data about served terminal devices torecognize predictable usage patterns. This can include sensing data thatindicates the positions of served terminal devices. Local learningsubsystem 2216 may comprises a processor that is capable of beingconfigured to execute a propagation modeling algorithm for predictingradio conditions and/or an access usage prediction algorithm forpredicting user behavior with radio access. The operation of thesealgorithms is described below and in the figures.

Local controller 2218 may be a processor configured to communicate witha counterpart central controller of anchor access point 2002. As furtherdescribed below, local controller 2218 may be configured to receive andcarry out control instructions provided by the central controller,execute a local trajectory algorithm to determine trajectories for themobile access nodes, and determine scheduling and resource allocations,fronthaul radio access technology selections, and/or routings.

Sensor 2220 may be a sensor configured to perform sensing and to obtainsensing data. In some aspects, sensor 2220 may be a radio measurementengine configured to obtain radio measurements as sensing data. In someaspects, sensor 2220 can be image or video sensors or any type ofproximity sensor (e.g., radar sensors, laser sensors, motion sensors,etc.) that can obtain sensing data that indicates positions of theserved terminal devices.

Relay router 2222 may be a processor configured to communicate with acounterpart user router of anchor access point 2002. As furtherdescribed below, the user router may send relay router 2222 downlinkuser data for the served terminal devices, which relay router may thentransmit to the served terminal devices via baseband subsystem 2206.Relay router 2222 may also receive uplink user data from the servedterminal devices, and may transmit the uplink user data to the userrouter of anchor access point 2002.

As shown in FIG. 23 , anchor access point 2002 may include antennasystem 2302, radio transceiver 2304, baseband subsystem 2306 (includingphysical layer processor 2308 and protocol controller 2310), andapplication platform 2312. Antenna system 2202, radio transceiver 2204,and baseband subsystem 2206 may be configured in a similar or samemanner as antenna system 302, radio transceiver 304, and basebandsubsystem 306 as shown and described for network access node 110 in FIG.3 . Antenna system 2302, radio transceiver 2304, and baseband subsystem2306 may therefore be configured to perform radio communications to andfrom mobile access nodes 2004 and 2006.

As shown in FIG. 23 , application platform 2312 may include mobileinterface 2314, central learning subsystem 2316, central controller2318, sensor hub 2320, and user router 2322. As previously introducedregarding anchor interface 2214, mobile interface 2314 may be aprocessor configured to communicate with anchor interface 2214 of mobileaccess nodes 2004 and 2006 on a logical connection that relies onwireless transmission for transport. Mobile interface 2314 may thereforetransmit and receive signaling to and from its peer anchor interfaces2214 at mobile access nodes 2004 and 2006.

Central learning subsystem 2316 may be a processor configured toexecute, for example, a pattern recognition algorithm, propagationmodeling algorithm, and/or access usage prediction algorithm. Thesealgorithms can be AI algorithms that use input data about servedterminal devices to predict user density, predict radio conditions, andpredict user behavior for access usage. The operation thereof is furtherdescribed below and by the figures.

Central controller 2318 may be a processor configured to determinecontrol instructions for mobile access nodes 2004 and 2006. As furtherdescribed below, the control instructions can include coarsetrajectories, scheduling and resource allocations, fronthaul radioaccess technology selections, and/or initial routings. In some aspects,central controller 2318 may be configured to execute a centraltrajectory algorithm to determine coarse trajectories for mobile accessnodes 2004 and 2006.

Sensor hub 2320 may be a server-type component configured to collectsensing data. The sensing data can be provided, for example, by theserved terminal devices, mobile access nodes 2004 and 2006, and/or otherremote sensors. Sensor hub 2320 may be configured to provide thissensing data to central learning subsystem 2316.

User router 2322 may be a processor configured to interface with relayrouter 2222 over a logical connection. User router 2322 may beconfigured to identify downlink user data addressed to served terminaldevices, and to identify which mobile access node to send the downlinkuser data to. User router 2322 may then send the downlink user data tothe relay router 2222 of the corresponding mobile access node. Userrouter 2322 may also be configured to receive uplink user data from therelay routers 2222 of mobile access nodes 2004 and 2006, and to send theuplink user data along its configured path (e.g., through the corenetwork and/or to an external network location).

Mobile access nodes 2004 and 2006 can have different capabilities invarious aspects. For example, in some aspects, mobile access nodes 2004and 2006 can have full cell functionality, including mobility controlfor terminal devices, scheduling and resource allocation, and physicallayer processing. Accordingly, in these aspects, mobile access nodes2004 and 2006 can act as full-service cells. For example, with referenceto FIG. 22 , protocol controller 2310 may be configured to handle thefull cell protocol stack for both user and control planes. This can varydepending on the radio access technology or technologies supported bymobile access nodes. For example, in the case of LTE, protocolcontroller 2310 can be configured with PDCP, RLC, RRC, and MACcapabilities.

In other aspects, mobile access nodes 2004 and 2006 may have limitedcell functionality (e.g., less than full cell functionality). As mobileaccess nodes 2004 and 2006 may therefore not have full cellfunctionality, anchor access point 2002 may provide the remaining cellfunctionality. For example, the protocol controllers 2210 of mobileaccess nodes 2004 and 2006 may be configured to handle some protocolstack layers and functions, while protocol controller 2310 of anchoraccess point 2002 may be configured to handle the remaining cellfunctionality. The specific distribution of cell functionality betweenmobile access nodes 2004 and 2006 versus anchor access point 2002 canvary in different aspects. For example, in some aspects protocolcontrollers 2210 of mobile access nodes 2004 and 2006 may handlescheduling and resource allocation (e.g., assignment of radio resourcesto served terminal devices for uplink and downlink) while protocolcontroller 2310 of anchor access point 2002 may handle mobility control(e.g., may handle handovers and other mobility management of terminaldevices connected to mobile access nodes 2004 and 2006). In otheraspects, protocol controllers 2210 of mobile access nodes 2004 and 2006may be configured to handle some user plane functions (e.g., some of theradio access technology-dependent processing on user plane data) whileprotocol controller 2310 of anchor access point 2310 may be configuredto handle the remaining user plane functions.

In other aspects, mobile access nodes 2004 and 2006 may only handlephysical layer processing while anchor access point 2002 providesprotocol stack cell functionality. Accordingly, protocol controller 2310of anchor access point 2002 may be configured to handle mobility controland scheduling and resource allocation capabilities for the terminaldevices served by mobile access nodes 2004 and 2006. Protocol controller2310 of anchor access point 2002 may also be configured to handle userplane functions above the physical layer. Mobile access nodes 2004 and2006 may therefore be configured to perform physical layer processing(with physical layer processors 2208) on data addressed to ororiginating from their respective served terminal devices, whileprotocol controller 2310 of anchor access point 2002 may be configuredto perform the remaining user plane processing.

In some of these aspects, mobile access nodes 2004 and 2006 maytherefore not include protocol controllers 2210. For example, as anchoraccess point 2002 may be configured to handle both the control and userplane protocol stack cell functionality, mobile access nodes 2004 and2006 may not support protocol stack cell functionality and may thereforenot include protocol controllers 2210. Instead, mobile access nodes 2004and 2006 may include physical layer processors 2208 for performingphysical layer processing.

In some aspects, anchor access point 2002 may handle physical layer andprotocol stack cell functionality while mobile access nodes 2004 and2006 handle only radio processing. Accordingly, protocol controller 2310and physical layer processor 2308 of anchor access point 2002 mayperform all of the physical layer and protocol stack processing, whileradio transceivers 2204 and antenna systems 2202 of mobile access nodes2004 and 2006 may perform radio processing. In some of these aspects,mobile access nodes 2004 and 2006 may therefore not include physicallayer processors 2208 and protocol controllers 2210.

In some of these aspects, mobile access nodes 2004 and 2006 may functionin a similar manner to remote radio heads (RRHs). These RRHs arenormally deployed in distributed base station architectures, where acentralized baseband unit (BBU) performs baseband processing (includingphysical and protocol stack layers) and a remotely deployed RRH performsradio processing and wireless transmission. Accordingly, in theseaspects, anchor access point 2002 may function in a manner similar tothe BBUs (by performing physical and protocol stack cell processing.)while mobile access nodes 2004 and 2006 function in a manner similar tothe RRHs (by performing radio processing and wireless transmission).

In some aspects, this distributed architecture for anchor access point2002 and mobile access nodes 2004 and 2006 can use distributed RANtechniques, including Cloud RAN (C-RAN). For example, in C-RAN, thebaseband processing for multiple base stations can be handled at acentralized location (e.g., at centralized core network servers).Similarly, anchor access point 2002 may be configured to handle thebaseband processing for mobile access nodes 2004 and 2006 while mobileaccess nodes 2004 and 2006 perform radio processing and transmission.

Accordingly, as described above there are numerous possibilities for thedistribution of cell functionality between anchor access point 2002 andmobile access nodes 2004 and 2006. Any of these cell functionalitydistributions can be utilized in the various aspects of this disclosure.

FIG. 24 shows exemplary message sequence chart 2400 illustrating theoperation of anchor access point 2002 and mobile access nodes 2004-2006according to some aspects. As shown in FIG. 24 , anchor access point2002 may first perform initialization and setup with mobile access nodes2004-2006 and the terminal devices served by mobile access nodes2004-2006 in stage 2402. In some aspects, stage 2402 may include amulti-phase procedure. This can include a first phase where the servedterminal devices connect with mobile access nodes 2004-2006, a secondphase where mobile access nodes 2004-2006 connect with anchor accesspoint 2002, and a third phase where the served terminal devices connectwith anchor access point 2002 (via mobile access nodes 2004-2006). Forexample, in the first phase, one or more terminal devices may connectwith mobile access node 2004 by exchanging signaling (e.g., including arandom access and registration procedure) with its protocol controller2210, and one or more terminal devices may connect with mobile accessnode 2006 by exchanging signaling with its protocol controller 2210. Inthe second phase, mobile access nodes 2004 and 2006 may connect withanchor access point 2002 by exchanging signaling between theirrespective anchor interfaces 2214 and mobile interface 2314 of anchoraccess point 2002. In the third phase, the served terminal devices ofmobile access nodes 2004-2006 may connect with anchor access point 2002either by using mobile access nodes 2004-2006 as relays or by havingmobile access nodes 2004-2006 register the served terminal devices withanchor access point 2002 on their behalf. For example, in some aspectsthe served terminal devices of mobile access node 2004 may transmitsignaling, addressed to anchor access point 2002, to mobile access node2004. Mobile access node 2004 may receive and process this signaling viaits baseband subsystem 2206. Relay router 2222 of mobile access node2004 may then relay the signaling to anchor access point 2002 bywirelessly transmitting it via baseband subsystem 2206. Anchor accesspoint 2002 may then receive the signaling at its protocol processor 2310and register the served terminal devices accordingly. In other aspects,the respective protocol controllers 2210 of mobile access nodes 2004 and2006 may exchange signaling with protocol controller 2210 of anchoraccess point 2002 to register their respective served terminal devices.

The initialization and setup of stage 2402 may establish the wirelesslinks between the involved devices. Accordingly, stage 2402 mayestablish fronthaul links 2108 and 2110 and anchor links 2104 and 2106.After the served terminal devices and mobile access nodes 2004 and 2006are connected with anchor access point 2002, the served terminal devicesmay be able to use mobile access nodes 2004 and 2006 to transmit andreceive user data. As shown in FIG. 24 , the served terminal devices mayperform data communications with mobile access nodes 2004 and 2006 instage 2404 a, and mobile access nodes may perform data communicationswith anchor access point 2002 in stage 2404 b. For example, in thedownlink direction, user router 2322 of anchor access point 2002 mayreceive user data addressed to a terminal device. User router 2322 maythen determine which mobile access node is serving the terminal device,such as mobile access node 2004. User router 2322 may then provide theuser data to baseband subsystem 2306, which may transmit the user dataover the corresponding anchor link, such as anchor link 2104. Mobileaccess node 2004 may then wirelessly receive and process the user dataat its baseband subsystem 2206, and provide the user data to relayrouter 2222 (which as previously indicated may have a logical connectionwith user router 2322). Relay router 2222 may then identify which servedterminal device the user data is addressed to and subsequently transmitthe user data to the served terminal device (over the correspondingfronthaul link) via baseband subsystem 2206.

In the uplink direction, a terminal device may transmit user data to itsserving mobile access node, such as mobile access node 2004. Mobileaccess node 2004 may then wirelessly receive and process the user datavia its baseband subsystem 2206, and provide the user data to relayrouter 2222. Relay router 2222 may then wirelessly transmit the userdata to user router 2322 of anchor access point 2002 via its basebandsubsystem 2206 and baseband subsystem 2306 of anchor access point 2002.

Mobile access nodes 2004 and 2006 may therefore provide access to theirrespective served terminal devices via the data communication of stages2404 a and 2404 b. As denoted by the arrows in FIG. 24 , mobile accessnodes 2004 and 2006 may continue this data communication, and maytherefore continue to provide access to their served terminal devicesover time. As previously described, the cell functionalities of mobileaccess nodes 2004 and 2006 can differ in various different aspects,where some aspects may provide mobile access nodes 2004 and 2006 withfull cell functionality, some aspects may provide mobile access nodes2004 and 2006 with some but not all cell functionality, and some aspectsmay limit the mobile access nodes 2004 and 2006 to radio processingcapabilities. Accordingly, mobile access nodes 2004 and 2006 may performthe data communications in stages 2418 a and 2418 b according to theircell functionality.

As mobile access nodes 2004 and 2006 are mobile, they may be able toadjust their trajectories over time to improve access performance. Forexample, mobile access nodes 2004 and 2006 may be able to positionthemselves relative to their served terminal devices to produce strongfronthaul links, which can yield higher data rates and reliability.Furthermore, as previously indicated, the served terminal devices may insome cases exhibit predictable usage patterns. This can includepredictable positioning of terminal devices at specific times. Forexample, with reference back to FIG. 20 , the served terminal devicesmay congregate in living room 2010 during late evening hours, or maycongregate in dining room 2012 during breakfast and dinner times.Accordingly, by identifying predictable usage patterns such as these forthe target coverage area, mobile access nodes 2004 and 2006 may be ableto proactively position themselves in locations that can effectivelyprovide access to their served terminal devices.

Mobile access nodes 2004 and 2006 and anchor access point 2002 maytherefore attempt to determine these predictable usage patterns andsubsequently use the predictable usage patterns to determinetrajectories for mobile access nodes 2004 and 2006. In some aspects,mobile access nodes 2004 and 2006 and anchor access point 2002 mayutilize sensing data to determine the predictable usage patterns. Forexample, mobile access nodes 2004 and 2006 and anchor access point 2002may execute a pattern recognition algorithm (at local learningsubsystems 2216 and central learning subsystem 2316) that uses sensingdata to attempt to identify predictable usage patterns in their servedterminal devices.

Accordingly, as shown in FIG. 24 , mobile access nodes 2004 and 2006 mayobtain and send sensing data to anchor access point 2002 in stage 2406.The sensing data can be any type of data that indicates the positions ofterminal devices that are served by mobile access nodes 2004 and 2006.Sensors 2220 of mobile access nodes 2004 and 2006 may obtain the sensingdata. For example, in some aspects, sensors 2220 may be radiomeasurement engines that are configured to measure wireless signalstransmitted by the served terminal devices and to obtain correspondingradio measurements. Accordingly, the respective sensors 2220 of mobileaccess nodes 2004 and 2006 may be configured to obtain these radiomeasurements as the sensing data, and provide the radio measurements toanchor interfaces 2214. The anchor interfaces 2214 of mobile accessnodes 2004 and 2006 may then transmit the radio measurements to mobileinterface 2314 of anchor access point 2002, which may provide the radiomeasurements to sensor hub 2320. Although FIG. 24 shows sensors 2220 aspart of application platform 2212, in some aspects sensors 2220 may beradio measurement engines that are part of baseband subsystem 2206.

In other aspects, sensors 2220 of mobile access nodes 2004 and 2006 maybe another type of sensor that can obtain sensing data related to thepositions of the served terminal devices. For example, sensors 2220 canbe image or video sensors, or any type of proximity sensor (e.g., radarsensors, laser sensors, motion sensors, etc.), and can obtain sensingdata that indicates positions of terminal devices and/or userspotentially carrying terminal devices. Sensors 2220 may similarly sendthis sensing data to sensor hub 2320 of anchor access point 2318. Insome aspects, sensors 2220 may include multiple types of sensors, andmay send multiple types of sensing data to sensor hub 2320.

In some aspects, the served terminal devices may also send sensing datato anchor access point 2002 in stage 2408. For example, in some aspectsthe served terminal devices may include positional sensors (e.g.,geopositional sensors, such as those based on satellite positioningsystems) configured to estimate their positions, and may send theresulting position reports to sensor hub 2320. In some aspects, theserved terminal devices may first send the position reports to mobileaccess nodes 2004 and 2006, which may then relay the position reports(e.g., via their relay routers 2222) to sensor hub 2320 of anchor accesspoint 2002.

In some aspects, sensor hub 2320 may also maintain connections withremote sensors. These remote sensors can be deployed around the targetcoverage area, and may generate and send sensing data to sensor hub 2320(e.g., via wireless or wireless links with anchor access point 2002,which can include direct links or IP-based internet links).

Sensor hub 2320 may therefore receive this sensing data that indicatesthe positions of the served terminal devices. As shown in FIG. 24 , insome aspects mobile access nodes 2004-2006 and the served terminaldevices may continue to provide sensing data to anchor access point2002. Sensor hub 2320 may therefore collect and store the sensing data,such as in its local memory. In some aspects, the sensing data may betime-stamped. For example, sensor 2220 of mobile access nodes 2004 and2006 may be configured to attach a timestamp to sensing data itgenerates. As referenced herein, these timestamps can be any informationabout time (e.g., are not limited to times expressed in hours inminutes). Additionally or alternatively, the served terminal devices maysimilarly attach timestamps to sensing data they generate and send toanchor access point 2002. Additionally or alternatively, sensor hub 2320may attach timestamps to sensing data it receives.

As the sensing data indicates positions of served terminal devices, thetimestamped sensing data may indicate positions of served terminaldevices at certain times. It may therefore be possible to evaluate thetimestamped sensing data to estimate predictable usage patterns by theserved terminal devices. For example, referring back to the example ofFIG. 20 , the timestamped sensing data may indicate that the positionsof the served terminal devices is probabilistically likely to be inliving room 2010 during late evening hours, and probabilistically likelyto be in dining room 2012 during lunch and dinner hours. Depending onthe context, similar predictable usage patterns can also be derivablefrom the timestamped sensing data according to any type of repeated userbehavior. Other examples include users congregating in office buildingsduring working hours (or, even more specifically, in particular officesor meeting rooms), users congregating in restaurants during mealtimehours, users congregating in shopping and retail areas during weekdayevenings and weekends, users congregating in public transit areas (e.g.,train or bus stations) during commuting hours, and any scenario in whichusers follow a repeating pattern. These predictable usage patterns maynot be completely deterministic; in other words, there may not be anabsolute certainty that the served terminal devices will always followthe predictable usage patterns. The predictable usage patterns insteadrefer to statistical data that indicates a probability that servedterminal devices follow a particular usage pattern.

Anchor access point 2002 may then perform central trajectory andcommunication control processing in stage 2410. For example, sensor hub2320 may provide the timestamped sensing data to central learningsubsystem 2316. Central learning subsystem 2316 may then execute thepattern recognition algorithm on the timestamped sensing data todetermine the predictable usage patterns. In various aspects, thepattern recognition algorithm can be an AI algorithm, such as a machinelearning algorithm, neural network algorithm, or reinforcement learningalgorithm. While any such algorithm capable of recognizing usagepatterns can be employed, FIG. 25 shows flow chart 2500 illustrating abasic flow of an exemplary pattern recognition algorithm according tosome aspects. As shown in FIG. 25 , central learning subsystem 2316 mayfirst evaluate the timestamped sensing data to identify locations thathave dense user distributions at respective times in stage 2502. Forexample, central learning subsystem 2316 may be configured to use thetimestamped sensing data to estimate terminal device positions overtime, and may then generate a time-dependent density plot with theterminal device positions (e.g., such as a heat map for user densitythat is plotted over time). Using the time-dependent density plot,central learning subsystem 2316 may then evaluate the user densitiesover time to identify certain locations (e.g., two- or three-dimensionalareas within the target coverage area) that have dense userdistributions at a given time (e.g., a user distribution, expressed inusers per unit area, exceeding a predefined threshold).

Then, central learning subsystem 2316 may be configured to pair eachlocation with a time at which the dense user distribution occurred instage 2504. The time can be, for example, a window of time during whichthe user distribution of the location was above a predefined threshold.Central learning subsystem 2316 may add the resulting location-timepairs to a pattern database (e.g., in its local memory) that records theoccurrence of dense user distributions at certain times and locations.

In some aspects, sensor hub 2320 may collect timestamped sensing dataover an extended period of time, such as over multiple days, weeks, ormonths. Accordingly, the timestamped sensing data may indicate terminaldevice positions that repeat over multiple days. Central learningsubsystem 2316 may therefore determine whether any of the locations havedense user distributions at similar times on different days in stage2506. For example, central learning subsystem 2316 may evaluate thepattern database to determine whether any of the location-time pairs(from stage 2504) from different days have matching locations and times(e.g., within a tolerance to account for small differences).

These matching time-location pairs may indicate that a dense userdistribution in a location at a particular time on multiple differentdays. This may consequently indicate a predictable usage pattern.Central learning subsystem 2316 may then calculate a strength metric foreach matching time-location pair in stage 2508. The strength metric mayindicate a probabilistic likelihood that the matching time-location pairis a predictable usage pattern (e.g., that there exists somenon-negligible probability that the dense user distribution will berepeated). In some aspects, central learning subsystem 2316 maydetermine the strength metric for a given matching location-time pairbased on the number of days that produced matching time-location pairs.For example, matching location-time pairs that occurred more often thanother matching location-time pairs may yield higher strength metrics, asthe higher occurrence rate may indicate a higher likelihood that thedense user distribution will be repeated.

In some aspects, central learning subsystem 2316 may consider days ofthe week when calculating the strength metrics in stage 2508. Forexample, as previously referenced, there may be some predictable usagepatterns that occur on, for example, workdays and others that occur onweekends. There may be other predictable usage patterns that occur onlyon, for example, one day per week (for example, a weekly meeting in agiven conference room, or a weekly television show that a family watchesevery week). The strength metrics for location-time pairs may thereforenot only depend on whether a dense user distribution occurs a highnumber of days, but also whether a dense user distribution regularlyoccurs on a same day of the week. In some aspects, central learningsubsystem 2316 may associate one or more days of the week with thelocation-time pairs (e.g., as recorded in the pattern database) thatspecify which days of the week the corresponding dense user distributionoccurs.

At the output of stage 2508, central learning subsystem 2316 maytherefore obtain location-time pairs with corresponding strength metricsthat indicate the probabilistic likelihood that the location-time pairis a usage pattern. The combinations of associated location-time pairs,strength metrics, and days of the week may each represent a predictableusage pattern related to predicted user density.

In some aspects, central learning subsystem 2316 can perform flow chart2500 as a continuous procedure. For example, central learning subsystem2316 may be configured to evaluate timestamped sensing data as itarrives (or, for example, at the end of each day or other predefinedinterval) to determine whether any dense user distributions occurred. Ifso, central learning subsystem 2316 may compare the location-time pairof the dense user distribution with the location-time pairs in thepattern database, and determine whether there are any matchinglocation-time pairs. If so, central learning subsystem 2316 maycalculate a strength metric for the location-time pair and use thelocation-time pair, strength metric, and any associated days of the weekas a predictable usage pattern.

As previously indicated, the procedure of flow chart 2500 is exemplary,and central learning subsystem 2316 may equivalently use other patternrecognition algorithms to determine the predictable usage patterns. Forexample, in other aspects, instead of identifying discrete patterns suchas location-time pairs of dense user distributions, central learningsubsystem 2316 may generate a time-dependent density plot as thepredictable usage patterns, where the time-dependent density plot showsa deterministic distribution of users over time. In these aspects,central learning subsystem 2316 may evaluate the sensing data, obtainedover an extended period of time, to predict user density in the targetcoverage area over time. As previously indicated, this can be similar toa heat map that plots the density of users in the target coverage areaover time. Accordingly, in contrast to identifying discrete patterns,central learning subsystem 2316 may develop a plot of user density overtime, where the density of users in a particular location and time canbe predicted using the density of the time-dependent density plot. Insome aspects, central learning subsystem 2316 may develop a plot of userdensity over time and day, where the time-dependent density plot canpredict the density of users in a given location at a given time and dayof the week.

The predictable usage patterns described above for FIG. 25 relate topredicted user density (e.g., where terminal devices are likely to belocated at certain times). In some aspects, central learning subsystem2316 may also incorporate predicted access usage and/or predicted radioconditions into the predictable usage patterns. For example, the sensingdata collected by sensor hub 2320 can include historical usageinformation that details the usage of the radio access network by theserved terminal devices. This historical usage information can beinformation such as average data rate or throughput, total amount ofdownloaded or uploaded data, frequency/periodicity of active access(e.g., how often the served terminal devices download or upload userdata on an active access connection), or any other information thatindicates how often the served terminal devices use the radio accessnetwork or how much data the served terminal devices transfer. In someaspects, baseband subsystem 2306 may be configured to collect thishistorical usage information (e.g., by monitoring the access connectionsof served terminal devices, which run through baseband subsystem 2306via mobile access nodes 2004 and 2006) and provide this historical usageinformation to sensor hub 2320. In some aspects, the served terminaldevices may be configured to monitor their own access usage and toreport the resulting historical usage information to sensor hub 2320. Insome aspects, baseband subsystems 2206 of mobile access nodes 2004 and2006 may be configured to monitor the access usage of their respectiveserved terminal devices and to report the resulting historical usageinformation to sensor hub 2320.

In some aspects, the historical usage information can be timestampedand/or geotagged. Accordingly, central learning subsystem 2316 may beable to evaluate the historical usage information over time and/or areato predict access usage by the served terminal devices. For example,central learning subsystem 2316 may be configured to execute an accessusage prediction algorithm on the historical usage information topredict access usage over time and/or area. In some aspects, centrallearning subsystem 2316 may be configured to use a similar algorithmflow to that of flow chart 2500 to predict the access usage. Forexample, when the historical usage information is timestamped andgeotagged, central learning subsystem 2316 may be configured to evaluatethe historical usage information to identify locations from which aheavy access usage occurs at certain times (e.g., data usage exceeding adata rate or throughput threshold). Central learning subsystem 2316 maythen pair the locations with a time at which the heavy access usageoccurred, and subsequently determine whether any locations have heavyaccess usage at similar times on different days. Central learningsubsystem 2316 may then calculate a strength metric for thelocation-time pairs, and treat the location-time pairs, strengthmetrics, and associated days of the week as predictable usage patterns.

In another example where the predictable usage patterns also includepredicted radio conditions, the sensing data can include radiomeasurements that characterize the radio environment in the targetcoverage area. These radio measurements can be made and reported tosensor hub 2320 of anchor access point 2002 by the served terminaldevices of mobile access nodes 2004 and 2006, can be made and reportedby sensors 2220 of mobile access nodes 2004 and 2006, or can be made atanchor access point 2002 (e.g., at its own sensors). In some aspects,the radio measurements can be geotagged, and can therefore indicate theposition of the transmitting device (that transmits the wireless signalof which the radio measurement is made) or of the receiving device (thatperforms the radio measurement).

Sensor hub 2320 may then provide these radio measurements to centrallearning subsystem 2316, which may be configured to execute apropagation modeling algorithm to predict the radio environment of thetarget coverage area as part of stage 2410. For example, the propagationmodeling algorithm may be configured to generate a radio map (e.g., anREM) by modeling the radio environment over the geographic area of thetarget coverage area using the radio measurements and associatedgeotags. The propagation modeling algorithm can use any type ofpropagation modeling technique, such as a basic propagation model (e.g.,free-space pathloss model, as previously described) or a propagationmodel based on radio maps (e.g., based on a REM, as previouslydescribed). The predicted radio conditions may also form part of thepredictable usage patterns, as it may estimate the radio environmentaround the served terminal devices (e.g., including estimation of theradio environment in the locations of the dense user distributions). Thepredicted radio conditions can also be time-dependent, and canapproximate radio conditions at different times of day depending onobserved changes in the radio measurements over time.

Accordingly, central learning subsystem 2316 may determine predictableusage patterns that relate to user density, access usage, and/or radioconditions. With reference back to FIG. 24 , anchor access point 2002may use the predictable usage patterns as part of the central trajectoryand communication control processing of stage 2410. For example, centrallearning subsystem 2316 may provide the predictable usage patterns tocentral controller 2318.

In some aspects, central controller 2318 may be configured to execute acentral trajectory algorithm, using the predictable usage patterns, thatdetermines coarse trajectories for mobile access nodes 2004 and 2006. Insome aspects, this central trajectory algorithm may be the same orsimilar to the central trajectory algorithm previously described forcentral trajectory controller 714 of FIGS. 7 and 10 . For example, thecentral trajectory algorithm may use a statistical model of the radioenvironment in the target coverage area, where the statistical model isbased on the predicted radio conditions of the predictable usagepatterns (as determined by central learning subsystem 2316). Thestatistical model may also approximate the positions of the users withthe predicted user density of the predictable usage patterns, and mayapproximate access usage (e.g., the extent to which the served terminaldevices use the radio access network to transfer data) with thepredicted access usage of the predictable usage patterns. Using thisstatistical model, the central trajectory algorithm may define afunction of an optimization criteria related to the radio environment.The optimization criteria can be, for example, a supported data rate forthe served terminal devices, a probability that the supported data forthe served terminal devices is above a predefined data rate threshold, alink quality metric, or a probability that the link quality metric forthe served terminal devices is above a predefined link qualitythreshold.

The function of the optimization criteria may depend on the trajectoriesof mobile access nodes 2004 and 2006. Accordingly, the centraltrajectory algorithm may be configured to determine coarse trajectoriesfor mobile access nodes 2004 and 2006 that increase (e.g., maximize) thefunction of the optimization criteria. This can include using gradientdescent (or another optimization algorithm) to iteratively step thecoarse trajectories of mobile access nodes 2004 and 2006 in thedirection that maximizes the function of the optimization criteria.

As the function of the optimization criteria also depends on thelocations of the served terminal devices, the predicted user density(determined by central learning subsystem 2316) may enable the centraltrajectory algorithm to accurately estimate the locations of the servedterminal devices. For example, when the predicted user density is alocation-time pair associated with certain days of the week, thestatistical model may approximate the locations of the served terminaldevices as being at the location at the corresponding time. Accordingly,optimization of the function of the optimization criteria can includeoptimizing the function of the optimization criteria under theassumption that the served terminal devices are located at the location(of the location-time pair) at the corresponding time. The centraltrajectory algorithm can use the strength metric to govern how strongthe assumption is that the served terminal devices are located at thelocation at the corresponding time. For example, for location-time pairsthat have a very high strength metric (e.g., users are nearly alwayscongregated at the location at the given time on the associated days ofthe week), the central trajectory algorithm may place a strongassumption that users will be congregated around the location at thecorresponding time (and vice versa for weaker strength metrics). Theresulting central trajectories may therefore be weighted towardoptimizing the function of the optimization criteria given servedterminal devices located according to the location-time pairs of thepredicted user density.

In another example where the predicted user density is a time-dependentdensity plot, the central trajectory algorithm may approximate thelocations of the served terminal devices with the time-dependent densityplot. Accordingly, at a given time, the time-dependent density plot mayestimate that some locations of the target coverage are denser thanothers (e.g., that users are congregated at a certain location).Accordingly, the central trajectory algorithm may calculate the coarsetrajectories with a greater assumption that the served terminal devicesare positioned around the denser areas of the time-dependent densityplot. The coarse trajectories may therefore be weighted towardsproviding access to areas of the target coverage area that have higherdensity in the time-dependent density plot.

Anchor access point 2002 may therefore determine coarse trajectories formobile access nodes 2004 and 2006 as part of the central trajectory andcommunication control processing of stage 2410. In some aspects, centralcontroller 2318 may also perform communication control using thepredictable usage patterns. This can include determining scheduling andresource allocations for the served terminal devices, selecting radioaccess technologies for the served terminal devices, and/or determininginitial routings for the served terminal devices. For example, in someaspects central controller 2318 may use the predictable usage patternsto determine scheduling and resource allocations for mobile access nodes2004 and 2006 to use for their served terminal devices. Although not solimited, this can be applicable when cell functionality (such asscheduling) is handled at anchor access point 2002 (on behalf of mobileaccess nodes 2004 and 2006). For example, central controller 2318 mayevaluate the predicted user density, predicted radio conditions, andpredicted access usage to determine scheduling and resource allocationsfor the served terminal devices to use when transmitting and receivingto mobile access nodes 2004 and 2006. In some aspects, centralcontroller 2318 may determine the scheduling and resource allocations aspart of the central trajectory algorithm, where central controller 2318determines the scheduling and resource allocations to optimize afunction of the optimization criteria.

Central controller 2318 may also select radio access technologies forthe served terminal devices to use when transmitting and receiving toand from mobile access nodes 2004 and 2006. For example, in some aspectsthe served terminal devices and mobile access nodes 2004 and 2006 (e.g.,their respective antenna systems 2202, RF transceivers 2204, andbaseband subsystems 2206) may support multiple radio accesstechnologies. These can include cellular radio access technologies(e.g., LTE or another 3GPP radio access technology, mmWave, or any othercellular radio access technology) and/or short-range radio accesstechnologies (e.g., WiFi, Bluetooth, or any other short-range radioaccess technology). As they support multiple radio access technologies,the served terminal devices and mobile access nodes 2004 and 2006 mayhave several different options to select from for use on fronthaul links2108 and 2110. Central controller 2318 can therefore be configured toselect which radio access technologies for the served terminal devicesand mobile access nodes 2004 and 2006 to use on fronthaul links 2108 and2110 as part of stage 2410. In some aspects, central controller 2318 maybe configured to select the radio access technologies as part of thecentral trajectory algorithm, where central controller 2318 selectsradio access technologies for the fronthaul links that optimize thefunction of the optimization criteria.

In some aspects, central controller 2318 may be configured to selectinitial routings for the served terminal devices as part of stage 2410.For example, central controller 2318 may be configured to select whichmobile access node the served terminal devices should use. In theexample of FIG. 20 , there may be two mobile access nodes (mobile accessnodes 2004 and 2006) for central controller 2318 to select between foreach served terminal device. In other examples, there can be anyquantity of mobile access nodes for central controller 2318 to selectbetween for the initial routings. In some aspects, central controller2318 may select the initial routings as part of the central trajectoryalgorithm, where central controller 2318 selects the initial routings tooptimize the function of the optimization criteria.

In some aspects, central controller 2318 may also use external contextinformation, in addition to the sensing data, for the processing instage 2410. This external context information can include, for example,information about the service profile of the served terminal devices,information about the user profile of the served terminal devices,information about capabilities of the served terminal devices (e.g.,supported radio access technologies, supported data rates, transmitpowers, etc.), or information about the target coverage area (e.g., suchas maps or locations of obstacles).

In some aspects, anchor access point 2002 may use such contextinformation as part of the central trajectory algorithm. For example,central controller 2318 may use context information about the targetcoverage area, such as maps or locations of obstacles, to define thestatistical model used to approximate the radio environment. Forinstance, the statistical model can approximate propagation based on amap of the target coverage area and the locations of obstacles withinthe target coverage area. In another example, central controller 2318may be configured to use context information about the capabilities ofthe served terminal devices as part of the statistical model. Forinstance, the capabilities of the served terminal devices may relate tothe transmission and reception performance of the served terminaldevices, and may therefore be relevant to propagation in the statisticalmodel. In another example, central learning subsystem 2316 may usecontext information about the target coverage area to determinepredictable usage patterns, such as by identifying rooms in a map of thetarget coverage area that are associated with a predictable usagepattern (e.g., that form a location at which users congregate at acertain time). In another example, central learning subsystem 2316 mayuse context information about service or user profiles when determiningpredictable usage patterns about predicted usage access (e.g., by usinga service or user profile to estimate how users will use the servedterminal devices).

In some aspects, mobile access nodes 2004 and 2006 and/or the servedterminal devices may provide the context information to anchor accesspoint 2002. In other aspects, anchor access point 2002 may receive thecontext information from an external location, such as a core network orexternal data server that stores the context information.

Anchor access point 2002 may therefore determine one or more of coarsetrajectories, scheduling and resource allocations, radio accesstechnologies for fronthaul links, or initial routings as part of thecentral trajectory and communication control processing in stage 2410.Then, anchor access point 2002 may send corresponding controlinstruction to mobile access nodes 2004 and 2006 in stage 2412. Forexample, central controller 2318 may provide the control instructions tomobile interface 2314, which may then transmit (via its basebandsubsystem 2306) the control instructions to the respective peer anchorinterfaces 2214 of mobile access nodes 2004 and 2004. The controlinstructions may specify any of coarse trajectories, scheduling andresource allocations, fronthaul radio access technologies selections, orinitial routings.

After receiving the control instructions from anchor access point 2002,anchor interfaces 2214 of mobile access nodes 2004 and 2006 may providethe control instructions to their respective local controllers 2218.Local controllers 2218 may then perform local trajectory andcommunication control processing in stage 2414. For example, when thecontrol instructions include a coarse trajectory, local controller 2218may provide the coarse trajectory to movement controller 2226. Movementcontroller 2226 may then control steering and movement machinery 2228 tomove mobile access nodes 2004 and 2006 according to their respectivecoarse trajectories in stage 2416.

In some cases where the control instructions include scheduling andresource allocations, local controller 2218 may provide the schedulingand resource allocations to protocol controller 2210 of mobile accessnodes 2004 and 2006. Protocol controller 2210 may then use thescheduling and resource allocations to generate scheduling and resourceallocation messages for the served terminal devices. Protocol controller2210 may then send the scheduling and resource allocation messages tothe served terminal devices.

In some cases where the control instructions include fronthaul radioaccess technology selections, local controller 2218 may provide thefronthaul radio access technology selections to protocol controller2210. Protocol controller 2210 may then generate a fronthaul radioaccess technology selection message and transmit the fronthaul radioaccess technology selection message to the served terminal devices.

In some cases where the control instructions include initial routings,local controller 2218 may provide the initial routings to protocolcontroller 2210. Protocol controller 2210 may then generate an initialrouting message and transmit the initial routing message to the servedterminal devices.

Mobile access nodes 2004 and 2006 may then perform data communicationswith the served terminal devices in stage 2422 a and perform datacommunications with anchor access point 2002 in stage 2418 b. Aspreviously described, mobile access nodes 2004 and 2006 may, in thedownlink direction, receive user data addressed to their respectiveserved terminal devices from anchor access point 2002 over anchor links2104 and 2106 (e.g., at their respective relay routers 2222 from userrouter 2322 of anchor access point 2002). Mobile access nodes 2004 and2006 may then wirelessly transmit the user data to the served terminaldevices over fronthaul links 2108 and 2110 (e.g., by relay routers 2222wirelessly transmitting the user data via baseband subsystems 2206). Inthe uplink direction, mobile access nodes 2004 and 2006 may wirelesslyreceive user data from their served terminal devices over fronthaullinks 2108 and 2110 (e.g., at baseband subsystems 2206, which mayprovide the user data to relay routers 2222). Mobile access nodes 2004and 2006 may then wirelessly transmit the user data to anchor accesspoint 2002 over anchor links 2104 and 2106 (e.g., by relay routers 2222sending the user data to user router 2322 of anchor access point 2002via baseband subsystems 2206). Mobile access nodes 2004 and 2006 maytherefore provide access to their served terminal devices.

Mobile access nodes 2004 and 2006 may perform these data communicationsin stages 2418 a and 2418 b according to the control instructionsprovided by anchor access point 2002. For example, mobile access nodes2004 and 2006 may move according to the coarse trajectories whileperforming the data communications (e.g., by movement controller 2226controlling steering and movement machinery 2228 to move mobile accessnodes 2004 and 2006 according to their respective coarse trajectories).Mobile access nodes 2004 and 2006 may also use the scheduling andresource allocations (included in the control instructions) to schedulecommunications and allocate resources for communications with the servedterminal devices over fronthaul links 2108 and 2110 (e.g., at theirrespective protocol controllers 2210). Mobile access nodes 2004 and 2006may also use the fronthaul radio access technology selections to controlwhich radio access technologies are used for fronthaul links 2108 and2110 (e.g., by protocol controllers 2210 controlling which radio accesstechnologies are used to transmit and receive over fronthaul links 2108and 2110). Mobile access nodes 2004 and 2006 may also use the initialroutings to control which of the served terminal devices theyrespectively serve (e.g., by protocol controllers 2210 controlling themobility of the served terminal devices so that the served terminaldevices use the selected mobile access node for their routing).

As denoted by the arrow in FIG. 24 , in some aspects mobile access nodes2004 and 2006 may repeat stages 2414-2418 b. For example, in someaspects, local controllers 2218 and/or local learning subsystems 2216may be configured to update the predictable usage patterns, coarsetrajectories, scheduling and resource allocations, fronthaul radioaccess technology selections, and/or initial routings.

For example, central controller 2318 of anchor access point 2002 may beconfigured to provide the predictable usage patterns to mobile accessnodes 2004 and 2006 as part of the control instructions in stage 2412.As previously indicated, the predictable usage patterns may betime-dependent. For example, predicted user densities may includelocation-time pairs and/or time-dependent density plots thatcharacterize predicted user density over time. Predicted radioconditions may also be defined over time, where radio conditions maydiffer at different times of day. Predicted access usage may similarlyvary over time. Accordingly, while the initial control instructionsprovided by central controller 2318 in stage 2412 may be relevant forthe current time, the predictable usage patterns may indicate differentuser densities, radio conditions, and/or access usage at differenttimes. Accordingly, in some aspects, local controllers 2218 of mobileaccess nodes 2004 and 2006 may be configured to use the predictableusage patterns to update the coarse trajectories, scheduling andresource allocations, fronthaul radio access technology selections,and/or initial routings over time (e.g., to determine updatedtrajectories, updated scheduling and resource allocations, updatedfronthaul radio access technology selections, and/or updated routings).

In one example, the predictable usage patterns may indicate a differentuser density at a later time, different radio conditions at the latertime, and/or different access usage at the later time. Local controllers2218 of mobile access nodes 2004 and 2006 may therefore be configured toexecute a local trajectory algorithm using the different user density,radio conditions, and/or access usage, and to determine updatedtrajectories for mobile access nodes 2004 and 2006. In some aspects,this local trajectory algorithm may function similarly to the centraltrajectory algorithm used by central controller 2318. For example, thelocal trajectory algorithm may be configured to re-define thestatistical model using the different user density, radio conditions,and/or access usage for the later time, and to then determine updatedtrajectories for mobile access nodes 2004 and 2006 that optimize thefunction of the optimization criteria (e.g., using gradient descent oranother optimization algorithm). In some aspects, local controllers 2218may also be configured to determine updated scheduling and resourceallocations, fronthaul radio access technology selections, and/orroutings based on the different user density, radio conditions, and/oraccess usage. In some aspects, the respective local controllers 2218 ofmobile access nodes 2004 and 2006 may operate independently of eachother, while in other aspects the respective local controllers 2218 ofmobile access nodes 2004 and 2006 may operate in a collaborative manner.

After determining updated trajectories, updated scheduling and resourceallocations, updated fronthaul radio access technology selections,and/or updated routings, local controllers 2218 of mobile access nodes2004 and 2006 may control mobile access nodes 2004 and 2006 to performdata communications accordingly. For example, local controllers 2218 mayprovide the respective updated trajectories to movement controllers2226, which may then respectively control steering and movementmachinery 2228 to move mobile access nodes 2004 and 2006 according tothe updated trajectories. Local controllers 2218 may provide the updatedscheduling and resource allocations to their respective protocolcontrollers 2210, which may then generate and send out scheduling andresource allocation messages for their respective served terminaldevices. Local controllers 2218 may likewise provide the updatedfronthaul radio access technology selections and/or updated routings totheir protocol controllers 2210, which may generate and send outfronthaul radio access technology selection messages and/or routingmessages for their respective served terminal devices. Mobile accessnodes 2004 and 2006 may then provide access to the selected terminaldevices over fronthaul links 2108 and 2110 and anchor links 2104 and2106.

In some aspects, mobile access nodes 2004 and 2006 may use their locallearning subsystems 2216 to execute its own pattern recognitionalgorithm, and to update the predictable usage patterns (originallydetermined by central learning subsystem 2316). For example, therespective sensors 2220 of mobile access nodes 2004 and 2006 may beconfigured to continue to obtain sensing data that indicates thepositions of the served terminal devices. This sensing data can berelated to current, past, or future positions of the served terminaldevices, and can therefore include current positions, velocity, and/oracceleration measurements. Sensors 2220 may then provide the sensingdata to the respective local learning subsystems 2216 of mobile accessnodes 2004 and 2006. The served terminal devices may also send sensingdata (e.g., position reports) to local learning subsystem 2216). Thelocal learning subsystems 2216 may then execute a pattern recognitionalgorithm with the sensing data to update the predictable usagepatterns. This can include updating any of predicted user densities,predicted access usage, or predicted radio conditions. In some aspects,the pattern recognition algorithm may function similarly to the patternrecognition algorithm used by central learning subsystem 2216. Forexample, local learning subsystem 2216 can use the pattern recognitionalgorithm to adapt the predictable usage patterns according to the mostrecent sensing data, such as by updating the location-time pairs ortheir corresponding strength metrics or by updating a time-dependentdensity plot.

In some aspects, local learning subsystem 2216 may additionally oralternatively be configured to update predicted access usage of thepredictable usage patterns based on historical usage information of thesensing data. For example, the historical usage information may indicatechanges in the access usage by the served terminal devices (e.g., asusers of the served terminal devices have changed their behavior, or asnew served terminal devices operated by new users are now present).Accordingly, local learning subsystem 2216 may be configured to executean access usage prediction algorithm to update the predicted accessusage by the served terminal devices. As this historical usageinformation is more recent than the historical usage information used bycentral learning subsystem 2316 in stage 2410, the predicted accessusage may be updated.

In some aspects, local learning subsystem 2216 may additionally oralternatively be configured to update predicted radio conditions of thepredictable usage patterns based on radio measurements of the sensingdata. For example, local learning subsystem 2216 may be configured toexecute a propagation modeling algorithm based on recent radiomeasurement (e.g., obtained by sensor 2220, or reported to locallearning subsystem 2216 by the served terminal devices). As the radiomeasurements are more recent than those originally used by centrallearning subsystem 2216 in stage 2410, the resulting predicted radioconditions may be updated.

Local learning subsystem 2216 may then provide these updated predictableusage patterns to local controller 2218 of mobile access nodes 2004 and2006. Local controller 2218 may then be configured to update the controlinstructions based on the updated predictable usage patterns. Forexample, in some aspects local controller 2218 may be configured toexecute a local trajectory algorithm based on the updated predictableusage patterns. This local trajectory algorithm can be similar to theouter or backhaul trajectory algorithms previously described regardingouter moving cells 702-706 and backhaul moving cells 708 and 810.Accordingly, the local trajectory algorithm may be configured to use theupdated predictable usage patterns to refine the coarse trajectories ofouter moving cells 2004 and 2006. For example, as the updatedpredictable usage patterns are different from the predictable usagepatterns originally used by central controller 2316 of anchor accesspoint 2002 to determine the coarse trajectories, there may be new oralternative trajectories that can better optimize the function of theoptimization criteria. Accordingly, local controllers 2218 of mobileaccess nodes 2004 and 2006 may be configured to execute respective localtrajectory algorithms to determine updated trajectories that optimizethe function of the optimization criteria (e.g., according to gradientdescent, or another optimization algorithm) based on the updatedpredictable usage patterns. As previously described for the centraltrajectory algorithm, the predicted user densities, predicted radioconditions, and predicted access usage may influence the statisticalmodel used by the local trajectory algorithm, such as by impacting theestimated positions of served terminal devices, estimated radioenvironment of the target coverage area, and estimated usage of theradio access network by the served terminal devices.

In some aspects, local controllers 2218 may then use the updatedpredictable usage patterns to update the other control instructions,such as scheduling and resource allocations, fronthaul radio accesstechnology selections, and/or initial routings. Local controller 2218may use a similar procedure as described above for central controller2318 to update the scheduling and resource allocations, fronthaul radioaccess technology selections, and/or initial routings based on theupdated predictable usage patterns.

After updating the control instructions, mobile access nodes 2004 and2006 may then execute data communications with the updated controlinstructions. This can include sending scheduling and resourceallocation messages, fronthaul radio access technology selectionmessages, and/or updated routing messages to their respective servedterminal devices (e.g., from their protocol processors 2210). The localcontrollers 2218 may also provide updated trajectories to movementcontrollers 2226, which may then control steering and movement machinery2228 to move mobile access nodes 2004 and 2006 according to the updatedtrajectories.

In some cases, the use of predictable usage patterns can produceperformance benefits for the served terminal devices. For example,mobile access nodes 2004 and 2006 may be able to use trajectories thatare determined based on predicted locations of the served terminaldevices. Accordingly, by determining trajectories that optimize afunction of the optimization criteria using the predictable usagepatterns to approximate user location, mobile access nodes 2004 and 2006may be able to intelligently position themselves in a manner thateffectively serves the served terminal devices. Mobile access nodes 2004and 2006 may similarly be able to use scheduling and resourceallocations, fronthaul radio access selections, and/or routings based onpredictable usage patterns, which can in turn increase performance.

In some aspects, mobile access nodes 2004 and 2006 may adjust theirtrajectories based on their power conditions. For example, in some casesmobile access nodes 2004 and 2006 may have definite power supplies, suchas rechargeable batteries, that gradually deplete over the course oftheir operation. Accordingly, mobile access nodes 2004 and 2006 mayperiodically recharge their power supplies. This can include docking ata docking charging station or using a wireless charging station. In somecases where mobile access nodes 2004 and 2006 recharge by docking at adocking charging station, mobile access nodes 2004 and 2006 may move tothe docking charging station and use a short-range charging interface torecharge their power supplies (e.g., a physical charging interface suchas a wire or a short-range wireless charger). In some cases where mobileaccess nodes 2004 and 2006 recharge with wireless charging, the wirelesscharging station may be directional (e.g., may directionally steerwireless charging beams). Due to the potential presence of obstacles,mobile access nodes 2004 and 2006 may recharge with the wirelesscharging station by moving to a location for which the wireless chargingstation can direct a wireless charging beam.

Mobile access nodes 2004 and 2006 may therefore periodically move tocertain locations to recharge. However, this movement may disrupt theirprovision of access to the served terminal devices. For example, movingto a docking charging station or to a wireless charging beam may movemobile access nodes 2004 and 2006 away from their served terminaldevices.

Accordingly, in some aspects, mobile access nodes 2004 and 2006 may beconfigured to adjust their trajectories to allow for recharging. FIG. 26shows an exemplary scenario in which mobile access node 2004 may adjustits trajectory to balance between recharging and providing access to itsserved terminal devices. As shown in FIG. 26 , mobile access node 2004may initially be using trajectory 2606. Trajectory 2606 can be a coarsetrajectory (e.g., assigned by anchor access point 2002) or an updatedtrajectory (e.g., updated by local controller 2218 of mobile access node2004), and may be plotted to provide access to the served terminaldevices (e.g., based on optimization of a function of an optimizationcriteria related to the radio environment of the served terminaldevices).

During movement of mobile access node 2004 along trajectory 2606, thebattery power of mobile access node 2004 may gradually deplete. Mobileaccess node 2004 may then determine that mobile access node 2004 shouldrecharge its power supply. For example, in some aspects, localcontroller 2218 may be configured to monitor the power supply of mobileaccess node 2004. When local controller 2218 determines that the powersupply meets a predefined condition (e.g. when the remaining batterypower falls below a battery power threshold), local controller 2218 maytrigger adjustment of the trajectory of mobile access node 2004 tofacilitate recharging.

For example, local controller 2218 may determine new trajectory 2604. Asshown in FIG. 26 , new trajectory 2604 may move mobile access node 2004towards charging station 2602. In some aspects, local controller 2218may determine new trajectory 2604 based on the served terminal devicesand charging station 2602, such as by determining new trajectory 2604 asa trajectory that optimizes a function of the optimization criteriawhile moving mobile access node 2004 towards charging station 2602. Insome aspects, local controller 2218 may use predictable usage patternsto model the served terminal devices when determining new trajectory2604.

In some aspects where charging station 2602 is a wireless chargingstation, mobile access node 2004 may be able to recharge with thewireless charging beam while still providing access to the servedterminal devices. However, there may be a tradeoff between the accessand recharging rate, where mobile access node 2004 may be able toprovide better access (e.g., a higher data rate or other link qualitymetric) when positioned closer to the served terminal devices and may beable to achieve a higher recharging rate when positioned closer tocharging station 2602. In some aspects, local controller 2218 maytherefore use a weighted function that depends on both the optimizationcriteria and a recharging rate (e.g., the rate at which the power supplyof mobile access node 2004). Local controller 2218 may thereforedetermine new trajectory 2604 as a trajectory that maximizes theweighted function. New trajectory 2604 may therefore be balanced betweenoptimizing access versus optimizing recharging rate.

In some aspects where charging station 2602 is a docking chargingstation, mobile access node 2004 may move to charging station 2602(e.g., close enough to physically dock with charging station, or withina certain distance close enough to support a short-range wirelesscharger) to recharge. In some cases, mobile access node 2004 may be ableto continue providing access to the served terminal devices (e.g., byrelaying data between the served terminal devices and anchor accesspoint 2002) when it is docked at charging station 2602. In otheraspects, mobile access node 2004 may temporarily interrupt provision ofaccess to the served terminal devices while it is docked at chargingstation 2602.

In some aspects, a mobile access node that departs from its trajectorymay notify other mobile access nodes of the departure. The other mobileaccess nodes can then adjust their trajectories to compensate for thedeparture of the mobile access node. This can be used when mobile accessnodes depart from their trajectory to recharge or for any other reason.

FIG. 27 shows an exemplary scenario where mobile access node 2004 maynotify mobile access node 2006 that it is departing from its trajectory.For example, as shown in FIG. 27 , mobile access node 2004 may initiallybe following trajectory 2706. Mobile access node 2004 may then adjustits trajectory to new trajectory 2706 (e.g., to move mobile access node2004 towards charging station 2702). New trajectory 2706, however, maymove mobile access node 2004 away from the served terminal devices,which negatively impact their radio access. Accordingly, mobile accessnode 2004 may notify mobile access node 2006 (and/or one or more othermobile access nodes that are nearby) that it has adjusted itstrajectory. For example, local controller 2218 of mobile access node2004 may transmit signaling (e.g., via wireless transmission using itsbaseband subsystem 2206) to local controller 2218 of mobile access node2006 that notifies mobile access node 2006 of the trajectory adjustment.

Mobile access node 2006 may then adjust its trajectory to compensate forthe trajectory adjustment of mobile access node 2004. For example, localcontroller 2218 of mobile access node 2006 may adjust the trajectory ofmobile access node 2006 from trajectory 2710 to new trajectory 2708. Asshown in FIG. 27 , new trajectory 2708 may move mobile access node 2006towards trajectory 2706 that mobile access node 2004 was originallyfollowing.

In some aspects, mobile access node 2004 may notify mobile access node2006 of the trajectory departure prior to adjusting its trajectory. Forexample, local controller 2218 of mobile access node 2004 may beconfigured to monitor the remaining battery power of the power supply ofmobile access node 2004. When the remaining battery power falls below afirst threshold, local controller 2218 of mobile access node 2004 may beconfigured to notify local controller 2218 of mobile access node 2006that mobile access node 2004 will adjust its trajectory. Localcontroller 2218 of mobile access node 2006 may therefore be able todetermine its new trajectory 2708 prior to mobile access node 2004actually departing from its trajectory. Then, when the remaining batterypower of mobile access node 2004 falls below a second threshold, localcontroller 2218 of mobile access node 2004 may notify local controller2218 of mobile access node 2006 that mobile access node 2004 will nowchange its trajectory. Local controller 2218 of mobile access node 2006may then execute new trajectory 2708.

FIG. 28 shows method 2800 of operating a mobile access node. As shown inFIG. 28 , method 2800 includes relaying data between one or more servedterminal devices and an anchor access point (2802), receiving controlinstructions from the anchor access point that include a coarsetrajectory and a predictable usage pattern of the one or more servedterminal devices (2804), controlling the mobile access node to moveaccording to the coarse trajectory while relaying data between the oneor more served terminal devices and the anchor access point (2806), andupdating the coarse trajectory based on the predictable usage pattern toobtain an updated trajectory (2808).

FIG. 29 shows method 2900 of operating a mobile access node. As shown inFIG. 29 , method 2900 includes relaying data between one or more servedterminal devices and an anchor access point (2902), obtaining sensingdata that indicates positions of the one or more served terminal devicesand sending the sensing data to the anchor access point (2904),receiving a coarse trajectory from the anchor access point that is basedon the sensing data (2906), and controlling the mobile access node tomove according to the coarse trajectory while relaying data between theone or more served terminal devices and the anchor access point (2908).

FIG. 30 shows method 3000 of operating a mobile access node. As shown inFIG. 30 , method 3000 includes relaying data between one or more servedterminal devices and an anchor access point (3002), receiving a coarsetrajectory from the anchor access point (3004), and controlling themobile access node to move according to the coarse trajectory whilerelaying data between the one or more served terminal devices and theanchor access point (3006).

FIG. 31 shows exemplary method 3100 of operating an anchor access pointaccording to some aspects. As shown in FIG. 31 , method 3100 includesexchanging data with one or more served terminal devices via a mobileaccess node (3102), determining a predictable usage pattern of the oneor more served terminal devices based on sensing data that indicatespositions of the one or more served terminal devices (3104), anddetermining a coarse trajectory for the mobile access node based on thepredictable usage pattern, and sending the coarse trajectory to themobile access node (3106).

Outdoor Mobile Access Nodes for Indoor Coverage

Network providers have introduced the concept of customer-premisesequipments (CPEs) for mobile broadband coverage. These CPEs aregenerally fixed devices similar to access points that are mounted on oroutside of a building. The CPEs can have a backhaul link to the network,and can therefore provide radio access to various terminal devicesinside of the building. These proposed CPEs are generally fixed in onelocation, and are therefore stationary. Accordingly, while the CPEs mayimprove access to indoor terminal devices due to their forwarddeployment, they may not be able to adapt to changing user positions andother dynamic conditions.

According to various aspects, mobile access nodes positioned outside ofindoor coverage areas may utilize trajectories that can be dynamicallyoptimized. As these mobile access nodes are both mobile and aware ofdynamic conditions in the indoor coverage area, they can adapt theirtrajectories over time to maintain strong radio links with the terminaldevices located in the indoor coverage area.

FIG. 32 shows an exemplary network scenario according to some aspects.As shown in FIG. 32 , mobile access nodes 3202-3206 may be deployedoutside of indoor coverage area 3212. Mobile access nodes 3202-3206 maybe mobile CPEs or any other type of moving network access node or cell.Indoor coverage area 3212 can be, for example, a private residence, acommercial building, or any other type of indoor coverage area. Indoorcoverage area 3212 can be completely or partially indoors (e.g., may ormay not have walls on all sides and may or may not have a roof or otherupper surface).

Mobile access nodes 3202-3206 may provide radio access to various servedterminal devices located inside of indoor coverage area 3212. Mobileaccess nodes 3202-3206 may therefore act as relays to receive, process,and retransmit data between the served terminal devices and networkaccess node 3208 over wireless backhaul links. Accordingly, in theuplink direction, mobile access nodes 3202-3206 may be configured toreceive uplink data originating from the served terminal devices inindoor coverage area 3212. Mobile access nodes 3202-3206 may thenprocess and retransmit the uplink data (e.g., using any type of relayingscheme) to network access node 3208 over wireless backhaul links.Network access node 3208 may then route the uplink data as appropriate,such as to external data networks via a core network to which networkaccess node 3208 is connected to. In the downlink direction, networkaccess node 3208 may obtain downlink data addressed to the servedterminal devices in indoor coverage area 3212, such as by receiving itfrom the core network. Network access node 3208 may then transmit thedownlink data to mobile access nodes 3202-3206 (e.g., to the mobileaccess node to which the destination terminal device is connected to)over wireless backhaul links. Mobile access nodes 3202-3206 may receivethe downlink data addressed to their respective served terminal devicesand then process and retransmit the downlink data to the correspondingserved terminal devices.

The trajectories (e.g., positioning) of mobile access nodes 3202-3206may impact the performance of the radio access provided to the servedterminal devices in indoor coverage area 3212. For example, trajectoriesof mobile access nodes 3202-3206 that position them close to indoorcoverage area 3212 may increase the link strength due to the reducedpropagation distance. Furthermore, mobile access nodes 3202-3206 may beable to position themselves proximate to the actual positions of servedterminal devices within indoor coverage area 3212, which can furtherimprove link strength.

Additionally, in some cases the propagation pathloss of indoor coveragearea 3212 (e.g., the outdoor-to-indoor propagation pathloss) may vary.FIG. 32 shows one example where indoor coverage area 3212 may haveopenings 3212 a-3212 f along its outer surface. Openings 3212 a-3212 fcan be, for example, doors or windows. As openings 3212 a-3212 f havelower propagation pathloss than the remaining outer surface of indoorcoverage area 3212 (e.g., the outer walls), wireless transmissionthrough openings 3212 a-3212 f may yield higher link strength thanwireless transmission through the remaining outer surface of indoorcoverage area 3212. In addition to openings like doors and windows,there may be other areas of the outer surface of indoor coverage area3212 that have lower propagation pathloss than others. For example,certain areas of the outer surface area may be made of differentmaterials and/or have different layers (e.g., stone/brick versussidewall, different levels of insulation, etc.), which may in turn yielddifferent propagation pathlosses. The propagation pathloss of the outersurface may therefore vary.

Accordingly, in some aspects, mobile access nodes 3202-3206 may beconfigured to use trajectories that are based on information about thepropagation pathloss of indoor coverage area 3212. As the varyingpropagation pathloss across the outer surface can produce some areas ofthe outer surface that have lower propagation pathloss than others,mobile access nodes 3202-3206 can position themselves in locations thatcan provide stronger links to served terminal devices inside of indoorcoverage area 3212.

FIG. 33 shows an exemplary internal configuration of mobile access nodes3202-3206 according to some aspects. While some examples in thefollowing description may focus on describing the functionality ofmobile access node 3202, these descriptions can also likewise apply toother mobile access nodes. Accordingly, in some aspects, multiple or allof mobile access nodes 3202-3206 can be configured according to anyexample presented using mobile access node 3202.

As shown in FIG. 32 , in some aspects network access node 3208 may alsointerface with central trajectory controller 3210. Central trajectorycontroller 3210 may then be configured to determine coarse trajectoriesand provide the coarse trajectories to mobile access nodes 3202-3206. Inother aspects, mobile access nodes 3202-3206 may be configured todetermine their own trajectories, and may therefore not use a centraltrajectory controller to obtain coarse trajectories.

As shown in FIG. 33 , mobile access node 3202 may include antenna system3302, radio transceiver 3304, baseband subsystem 3306, applicationplatform 3312, and movement system 3326. In some aspects, antenna system3302, radio transceiver 3304, and movement system 3322 may be configuredin the manner of antenna system 2202, radio transceiver 2204, andmovement system 2224 described above for mobile access nodes 2004-2006in FIG. 22 .

As shown in FIG. 33 , application platform 3312 may include centralinterface 3314, node interface 3316, local learning subsystem 3318,local controller 3320, sensor 3322, and relay router 3324. In someaspects, central interface 3314 may be a processor configured tomaintain a signaling connection (e.g., a logical, software-levelconnection) with a peer node interface of central trajectory controller3210. Central interface 3314 may therefore support a signalingconnection between mobile access node 3202 and central trajectorycontroller 3210, where central interface 3314 may transmit and receivesignaling over the signaling connection via baseband subsystem 3306.Central interface 3314 may therefore provide data addressed to centraltrajectory controller 3210 to baseband subsystem 3306, which may thenwirelessly transmit the data (e.g., to network access node 3208, whichmay interface with central trajectory controller 3210). Basebandsubsystem 3306 may also wirelessly receive data originating from centraltrajectory controller 3210 (e.g., that is wirelessly transmitted bynetwork access node 3208), and may provide the data to central interface3314. Further references to communications between mobile access node3202 and central trajectory controller 3210 are understood as referringto such a communication arrangement.

Node interface 3316 may be a processor configured to maintain asignaling connection with a peer node interface of one or more othermobile access nodes, such as mobile access nodes 3204 and 3206. Nodeinterface 3316 may therefore support a signaling connection betweenmobile access node 3202 and mobile access nodes 3204 and 3206, wherenode interface 3316 may transmit and receive signaling over thesignaling connection via baseband subsystem 3306. Node interface 3316may therefore provide data addressed to other mobile access nodes tobaseband subsystem 3306, which may then wirelessly transmit the data tothe other mobile access nodes. Baseband subsystem 3306 may alsowirelessly receive data originating from other mobile access nodes, andmay provide the data to node interface 3316. Further references tocommunications between mobile access node 3202 and other mobile accessnodes are understood as referring to such a communication arrangement.

Local learning subsystem 3318 may be configured in the manner of locallearning subsystem 2216 of FIG. 22 , and may therefore be a processorconfigured to learning-based processing. In some local learningsubsystem 3318 may be configured to execute a pattern recognitionalgorithm, propagation modeling algorithm, and/or an access usageprediction algorithm as described above for local learning subsystem2216. These algorithms are described in detail below.

Local controller 3320 may be a processor configured to control theoverall operation of mobile access node 3202 related to trajectories. Insome aspects, local controller 3320 may be configured to receive andcarry out instructions provided by central trajectory controller 3210,such as for coarse trajectories. Local controller 3320 may also beconfigured to execute a local trajectory algorithm to determinetrajectories for mobile access node 3202.

Sensor 3322 may be configured in the manner of sensor 2220 of FIG. 22 ,and may therefore be a sensor configured to perform sensing and toobtain sensing data. In some aspects, sensor 3322 may be a radiomeasurement engine configured to obtain radio measurements as sensingdata. In some aspects, sensor 2220 can be image or video sensors or anytype of proximity sensor (e.g., radar sensors, laser sensors, motionsensors, etc.) that can obtain sensing data that indicates positions ofthe served terminal devices.

Relay router 3324 may be a processor configured to relay data betweennetwork access node 3208 and served terminal devices in indoor coveragearea 3212. Accordingly, relay router 3324 may be configured to identifydownlink data (received by baseband subsystem 3306 over the wirelessbackhaul link with network access node 3208) addressed to terminaldevices served by mobile access node 3202, and to transmit the downlinkdata to the served terminal devices via baseband subsystem 3306. Relayrouter 3324 may also be configured to identify uplink data (received bybaseband subsystem 3306 over wireless fronthaul links with servedterminal devices) originating from the served terminal devices, and totransmit the uplink data to network access node 3208 via basebandsubsystem 3306.

FIG. 34 shows an exemplary internal configuration of central trajectorycontroller 3210 according to some aspects. As shown in FIG. 34 , centraltrajectory controller 3210 may include node interface 3402, input datarepository 3404, trajectory processor 3406, and central learningsubsystem 3408. In some aspects, node interface 3402 may be a processorconfigured to act as a peer to central interface 3314 of mobile accessnode 3202, and may therefore be configured to support a signalingconnection between central trajectory controller 3210 and mobile accessnode 3202. As shown in FIG. 32 , central trajectory controller 3210 mayinterface with network access node 3208. Node interface 3402 maytherefore transmit signaling to mobile access node 3202 over thissignaling connection by providing the signaling to network access node3208, which may wirelessly transmit the signaling over the wirelessbackhaul link. Node interface 3402 may receive signaling from mobileaccess node 3202 by receiving the signaling from network access node3208, which may in turn have initially received the signaling frommobile access node 3202 over the wireless backhaul link.

Input data repository 3404 and trajectory processor 3406 may beconfigured in the manner of input data repository 1004 and trajectoryprocessor 1006 of central trajectory controller 714 in FIG. 10 .Accordingly, input data repository 3404 may be a server-type componentincluding a controller and the memory, where input data repository 3404collects input data for a central trajectory algorithm executed bytrajectory processor 3406. Trajectory processor 3406 may be configuredto execute the central trajectory algorithm with the input data and toobtain coarse trajectories for mobile access nodes 3202-3206.

In some aspects, central learning subsystem 3408 may be configured inthe manner of central learning subsystem 2316 of anchor access point2002 in FIG. 23 . Accordingly, central learning subsystem 3408 may be aprocessor configured to execute a pattern recognition algorithm,propagation modeling algorithm, and/or access usage predictionalgorithm. These algorithms can be AI algorithms that use input dataabout served terminal devices to predict user density, predict radioconditions, and predict user behavior for access usage.

As previously indicated, in some aspects mobile access nodes 3202-3206may operate in cooperation with central trajectory controller 3210(e.g., may use trajectories determined in part by central trajectorycontroller 3210), while in other aspects mobile access nodes 3202-3206may operate independently from a central trajectory controller (e.g.,may determine their trajectories locally, optionally in cooperation withother mobile access nodes). FIG. 36 shows exemplary message sequencechart 3600 according to some aspects, which shows an example wheremobile access nodes 3202-3206 may operate in coordination with centraltrajectory controller. In some aspects, the procedure of messagesequence chart 3600 may be similar to that of message sequence chart1400 of FIG. 14 , in which central trajectory controller 714 andbackhaul moving cells 708 and 710 determined coarse and updatedtrajectories (as well as initial routings) for various outer movingcells and/or terminal devices that were served by backhaul moving cells708 and 710.

Accordingly, in some aspects message sequence chart 3600 may use a sameor similar procedure as message sequence chart 1400 to determine coarseand updated trajectories (and, optionally, routings) for mobile accessnodes 3202-3206 to serve indoor coverage area 3212. For example, mobileaccess nodes 3202-3206 may first perform initialization and setup withcentral trajectory controller 3210, which can include setting up thesignaling connections between the respective central interfaces 3314 ofmobile access nodes 3202-3206 and node interface 3402 of centraltrajectory controller 3210 (e.g., as previously described for stage 1402of FIG. 14 ). Then, central trajectory controller 3210 may computecoarse trajectories and initial routing for mobile access nodes3202-3206 in stage 3504. Similar to as described above for stage 1404,central trajectory controller 3210 may execute a central trajectoryalgorithm with its trajectory processor 3406. Trajectory processor 3406may therefore use input data collected and provided by input datarepository 3404 to develop a statistical model of the radio environmentaround indoor coverage area 3212. Then, using the statistical model toapproximate the radio environment, trajectory processor 3406 (runningthe central trajectory algorithm) may determine coarse trajectories formobile access nodes 3202-3206 that increase (e.g., maximize) a functionof an optimization criteria. The optimization criteria can be, forexample, a supported data rate for the served terminal devices, aprobability that the supported data rate for all of served terminaldevices is above a predefined data rate threshold, a link quality metric(e.g., SINR), or a probability that the link quality metric for all ofthe served terminal devices is above a predefined link qualitythreshold.

In some aspects, trajectory processor 3406 may balance the coarsetrajectories of mobile access nodes 3202-3206 between fronthaul andbackhaul. For example, the optimal position for mobile access node 3202to provide access to served terminal devices in indoor coverage area3212 may not be the optimal position for mobile access node 3202 toperform backhaul transmission or reception with network access node3208. In some aspects, the function of the optimization criteria maydepend on both fronthaul and backhaul (e.g., may consider both thefronthaul and backhaul link in representing the optimization criteria),and determining coarse trajectories to optimize the function of theoptimization criteria may inherently consider both the fronthaul andbackhaul. In other aspects, the function of the optimization criteriamay, for example, only be based on the fronthaul (e.g., may representsupported data rate and/or link quality depending on the fronthaul butnot the backhaul). In such cases, trajectory processor 3406 may beconfigured to use a dual-phase optimization approach. For example,trajectory processor 3406 may be configured to determine a coarsetrajectory based on the function of the optimization criteria in thefirst phase, which only depends on the fronthaul. Trajectory processor3406 may then update the coarse trajectory to improve the backhaul inthe second phase (e.g., by adjusting the trajectory to optimize afunction depending on the backhaul, such as to increase a functiondefining link strength of the backhaul link or decrease a functiondefining the distance between the mobile access nodes and network accessnode 3208). Trajectory processor 3406 may then return to the first phaseto update the coarse trajectory to increase the function of theoptimization criteria, and continue to alternate between the first andsecond phases to iteratively update the coarse trajectory. In oneexample, trajectory processor 3406 may perform these updates in anincremental manner, such as by updating the trajectories in limitedsteps with each update.

In some aspects, the central trajectory algorithm may be configured touse propagation pathloss data about indoor coverage area 3212 as inputdata. This propagation pathloss data can characterize the propagationpathloss on the outer surface of indoor coverage area. For example, thepropagation pathloss data can be map-based data that geographicallyplots the propagation pathloss (e.g., with discrete values for eachpoint or a continuous function along a line) along the outer surface ofindoor coverage area 3212. This can be coordinate-based data, where thedata includes coordinates along the outer surface and each coordinate ispaired with a propagation pathloss value (that gives the propagationpathloss for wireless signals passing through the outer surface at thecorresponding coordinate). The underlying propagation pathloss data cantherefore be a set of map coordinates that are paired with a propagationpathloss value for the location corresponding to the map coordinates.The propagation pathloss data can be either two-dimensional (e.g., eachcoordinate having two values to identify a point on a 2D plane) orthree-dimensional (e.g., each coordinate having three values to identifya point in a 3D area).

In some aspects, this map-based propagation pathloss data can bedownloaded or preinstalled into central trajectory controller 3210. Forexample, a human operator can render the propagation pathloss data(e.g., with a computer-aided design tool, such as a mapping tool) forthe outer surface of indoor coverage area 3212, and input datarepository 3404 can download and store the propagation pathloss data forlater use.

In other aspects, central trajectory controller 3210 may be configuredto locally generate the propagation pathloss data. For example, theserved terminal devices, mobile access nodes 3202-3206 (e.g., withsensor 3322 configured as a radio measurement engine), and or externalsensors may perform and report radio measurements to input datarepository 3404. The radio measurements can also be geotagged, such aswith the location of the transmitting device for the radio measurementor the receiving device for the radio measurement. Input data repository3404 may then provide the radio measurements to central learningsubsystem 3408. Central learning subsystem 3408 may then execute a radiopropagation modeling algorithm with radio measurements to estimate thepropagation pathloss of the outer surface of indoor coverage area 3212and to generate the propagation pathloss data. This can include usingthe geotagging information accompanying the radio measurements toestimate the propagation pathloss. For example, if a radio measurementis geotagged with both the transmitting and receiving device's locations(e.g., a location of a served terminal device and a mobile access nodethat performs a radio measurement on the served terminal device), thepropagation modeling algorithm can determine approximately where theradio signal passed through the outer surface. Using the radiomeasurement and the distance between the transmitting and receivingdevices (which is generally inversely proportional to signal strength),the propagation modeling algorithm can estimate the propagation pathlossat the point where the radio signal passed through the outer surface. Inother cases where radio measurements are only geotagged at one side(e.g., with the location of only the transmitting device or thereceiving device), the propagation modeling algorithm may still be ableto estimate a region of the outer surface where the radio signal passedthrough the outer surface, and can thus derive propagation pathloss datafrom the radio measurements. The radio measurements can also begeotagged with Angle-of-Arrival (AoA) information about the angle atwhich the receiving device received the radio signal, which cansimilarly be used to estimate the point at which the radio signal passedthrough the outer surface. In some aspects, other context information,such as a map of indoor coverage area 3212, can be used to approximate,for example, where a served terminal device was when it transmitted aradio signal. The propagation modeling algorithm can then use thisapproximate location of the served terminal device to estimate the pointwhere the radio signal passed through the outer surface, as well as thedistance between the served terminal device and a mobile access nodemeasuring the radio signal. The propagation modeling algorithm can thenapproximate the propagation pathloss for an approximate point on theouter surface. In some aspects, the propagation modeling algorithm canuse other radio map data (e.g., such as an REM) that indicates thepropagation pathlosses from other obstacles in the path between theserved terminal device and the mobile access node to isolate thepropagation pathloss that is due to the outer surface. In some aspects,central learning subsystem 3408 may use a large data set of such radiomeasurements to develop the propagation pathloss data for the outersurface of indoor coverage area 3212.

Central learning subsystem 3408 can therefore generate the propagationpathloss data as map-based data that plots propagation pathloss valuesalong the outer surface of indoor coverage area 3212. In some aspects,central learning subsystem 3408 may use a map of indoor coverage area3212, such as by tagging locations in the map (e.g., attaching data tothe stored coordinates of these locations) that are located on the outersurface indoor coverage area 3212 with a propagation pathloss value.

Additionally or alternatively, in some aspects central learningsubsystem 3408 may be configured to use propagation pathloss data thatidentifies low propagation pathloss areas along the outer surface ofindoor coverage area 3212. In some cases, this propagation pathloss datacan be less specific than the map-based propagation pathloss data, as itmay only identify locations of finite number of low propagation pathlossareas instead of plotting out propagation pathloss values along theouter surface of indoor coverage area 3212. This is referred to hereinas location-based propagation pathloss data. For example, with referenceto FIG. 32 , this location-based propagation pathloss data can identifythe locations of openings 3212 a-3212 f as locations of low propagationpathloss areas. The underlying propagation pathloss data can thereforebe map coordinates that identify the location of a low propagationpathloss area along the outer surface of indoor coverage area 3212. Thislocation-based propagation pathloss data can be based on a map of indoorcoverage area 3212, where locations (e.g., their coordinates) are taggedas being a low propagation pathloss area. Furthermore, in some aspectsthe low propagation pathloss areas can be paired with a propagationpathloss rating on a predefined scale, where the ratings indicatedifferent propagation pathloss values. In an example where opening 3212d is a door and opening 3212 a is a window, the coordinates for opening3212 d (in the propagation pathloss data) can be paired with apropagation pathloss rating that indicates more propagation pathlossthan the coordinates for opening 3212 a. These propagation pathlossratings may be less specific than the propagation pathloss valuesdescribed above for the map-based propagation pathloss data.

In some aspects, this location-based propagation pathloss data can bedownloaded or preinstalled into central trajectory controller 3210. Forexample, a human operator can render the propagation pathloss data(e.g., with a computer-aided design tool, such as a mapping tool) forthe outer surface of indoor coverage area 3212, such as by tagging avirtual map at the locations that are low propagation pathloss areas.Input data repository 3404 can then download and store the propagationpathloss data for later use.

In other aspects, central learning subsystem 3408 may execute apropagation modeling algorithm to generate the location-basedpropagation pathloss data. For example, similar to as described before,input data repository 3404 may collect radio measurements from aroundindoor coverage area 3212. Central learning subsystem 3408 may thenexecute the propagation modeling algorithm on the radio measurements andattempt to identify the locations of low propagation pathloss areas onthe outer surface of indoor coverage area 3212. For example, asdescribed above, central learning subsystem 3408 may be configured toestimate the positions of the transmitting and receiving devices basedon the radio measurements (e.g., potentially using geotagging data), thepoint where the radio signal passed through the outer surface, and thedistance between the transmitting and receiving devices. Using theinverse relationship between distance and signal strength, centrallearning subsystem 3408 may then estimate the propagation pathloss atthe point on the outer surface and determine whether the point is haslow propagation pathloss or not (e.g., propagation pathloss below athreshold). Central learning subsystem 3408 may do this with a large setof radio measurements, and therefore obtain determinations whether acorresponding large group of points on the outer surface have lowpropagation pathloss. Central learning subsystem 3408 may then evaluatethe points on the outer surface that are identified as being lowpropagation pathloss, and identify areas of the outer surface that havea high density of points with low propagation pathloss (e.g., a densityof points above a threshold) as being low propagation pathloss areas. Insome aspects, central learning subsystem 3408 may also assign apropagation pathloss rating to the identified low propagation pathlossareas, where the rating can be based on the estimated propagationpathlosses of the points in the low propagation pathloss areas (e.g.,based on an average or other combined metric of the estimatedpropagation pathlosses of the points).

The propagation pathloss data (e.g., map-based, location-based, oranother type of propagation pathloss data) may therefore generallycharacterize propagation pathloss on the outer surface of indoorcoverage area 3212. As previously indicated, in some aspects, indoorcoverage area 3212 may only be partially indoors, such as a buildingwith only three walls. In these cases, the propagation pathloss data maycharacterize openings resulting from partially indoor buildings (e.g., amissing wall, partially outdoor room and the like) as having a lowpropagation pathloss value and/or rating.

With reference back to message sequence chart 3500 in FIG. 35 , thecentral trajectory algorithm running at trajectory processor 3406 cantherefore use the propagation pathloss data as part of the statisticalmodel to model the propagation pathloss through the outer surface duringstage 3504. This can be particularly applicable when the statisticalmodel is based on a radio map that models the radio environment over amapped area, as the map-based or location-based propagation pathlossdata can be inserted into the radio map along with other input data usedto generate the radio map. Using the propagation pathloss data as partof the statistical model, trajectory processor 3406 may execute thecentral trajectory algorithm to determine coarse trajectories for mobileaccess nodes 3202-3206 that increase, which may include maximizing, thefunction of the optimization criteria in stage 3504. This can be done,for example, using gradient descent or another optimization approach.

As the statistical model is based on the propagation pathloss data, thecoarse trajectories may help to position mobile access nodes 3202-3206in locations from which they can serve terminal devices inside indoorcoverage area 3212 with low propagation pathloss. For example, as thepropagation pathloss data may provide an accurate characterization ofthe propagation pathlosses through the outer surface of indoor coveragearea 3212, the central trajectory may be able to effectively determinecoarse trajectories that yield radio links between mobile access nodes3202-3206 that pass through low propagation pathloss areas in the outersurface. FIG. 32 shows an example of this, where mobile access nodes3202-3206 may be able to use radio links that pass through lowpropagation pathloss areas (e.g., openings 3212 a, 3212 e, and 3212 f).As the propagation pathloss data may characterize the propagationpathloss of the outer surface at various different positions, thestatistical model may be able to accurately approximate propagationpathloss between mobile access nodes, and thus can be used by thecentral trajectory algorithm to determine coarse trajectories that yieldradio links having lower propagation pathloss.

In some aspects central trajectory controller 3210 may also determineinitial routings (e.g., assign the terminal devices to one of mobileaccess nodes 3202-3206) that increase the function of the optimizationcriteria. Central trajectory controller 3210 may determine these initialroutings using any processing technique described above for centraltrajectory controller 714. As central trajectory controller 3210 mayalso determine the initial routings based on the statistical model, theinitial routings may also be dependent on the propagation pathloss data.For example, as the propagation pathloss data indicates areas on theouter surface of indoor coverage area 3212 that have low propagationpathloss, central trajectory controller 3210 may be configured todetermine initial routings (e.g., select which of mobile access nodes3202-3206 to assign to relay data for each served terminal device) thatyield radio links between the mobile access nodes and served terminaldevices that pass through the outer surface at areas with lowerpropagation pathloss.

In some aspects, central trajectory controller 3210 may use predictableusage patterns as part of the statistical model in stage 3504.Accordingly, central trajectory controller 3210 can use predictableusage patterns (e.g., generated by central learning subsystem 3408) inany manner described above for FIGS. 20-31 . For example, centraltrajectory controller 3210 may be configured to use predicted userdensities, predicted radio conditions, and/or predicted usage patternsas part of the statistical model when executing the central trajectoryalgorithm. Central trajectory controller 3210 may therefore determinethe resulting coarse trajectories and/or initial routings determined instage 3504 based on these predictable usage patterns. In some aspects,central trajectory controller 3210 may also use predictable usagepatterns determining scheduling and resource allocations and/orselecting fronthaul radio access technologies.

Stages 3508-3514 may then generally follow the procedure previouslydescribed for message sequence chart 4100, and will be explained brieflyhere for purposes of conciseness. As shown in FIG. 35 , centraltrajectory controller 3210 may send the coarse trajectories and initialroutings to mobile access nodes 3202-3206 in stage 3506. Mobile accessnodes 3202-3206 may establish connectivity with the served terminaldevices in indoor coverage area 3212 (e.g., as specified by the initialroutings). Mobile access nodes 3202-3206 may then relay data between theserved terminal devices and the radio access network (e.g., networkaccess node 3208) in stages 3510 a-3510 b while moving according to thecoarse trajectories. As central trajectory controller 3210 determinedthe coarse trajectories using propagation pathloss data of the outersurface of indoor coverage area 3212, mobile access nodes 3202-3206 mayuse trajectories that position mobile access nodes 3202-3206 inpositions that yield stronger links (through the outer surface of indoorcoverage area 3212) with the served terminal devices. This can thereforehelp improve radio performance (e.g., reduce SNR)

Mobile access nodes 3202-3206 and the served terminal devices may thenperform parameter exchange in stage 3512, such as where the servedterminal devices report radio measurements back to mobile access nodes3202-3206. With mobile access node 3202 as an example, local controller3320 of mobile access node 3302 may receive the radio measurements fromthe served terminal devices via baseband subsystem 3306, and store themfor use as input data in the local trajectory algorithm. Mobile accessnodes 3202-3206 may also perform their own radio measurements on signalsreceived from the served terminal devices. For example, sensor 3322 maybe configured as a radio measurement engine, and may provide theresulting radio measurements to local controller 3320.

Mobile access nodes 3202-3206 may then perform local optimization oftrajectories and/or routing in stage 3514. In an example using mobileaccess node 3202, local controller 3320 may be configured to execute thelocal trajectory algorithm to update the coarse trajectories based oninput data. The input data can include the radio measurements. In someaspects, the local trajectory algorithm may determine an updatedtrajectory for mobile access node 3202 that increases, which may includemaximizing, a function of the optimization criteria.

In some aspects, mobile access node 3202 may use local learningsubsystem 3318 to update the propagation pathloss data. For example,central trajectory controller 3210 may have previously sent thepropagation pathloss data for indoor coverage area 3212 to mobile accessnode 3202 (e.g., during stage 3506), which mobile access node 3202 maystore at local learning subsystem 3318. Mobile access node 3202 may alsoprovide the radio measurements to local learning subsystem 3318. Locallearning subsystem 3318 may then update the propagation pathloss datausing the radio measurements. For example, local learning subsystem 3318may use geotagged radio measurements to estimate the point where theradio signal passed through the outer surface of indoor coverage area3212, the distance between the transmitting and receive devices, and thecorresponding propagation pathloss of the outer surface of indoorcoverage area 3212. Local learning subsystem 3318 may then use thispropagation pathloss to update the propagation pathloss data, such as byupdating a propagation pathloss value of map-based propagation pathlossdata at coordinates at or near the point, updating a propagationpathloss rating for location-based propagation pathloss data in a lowpropagation pathloss area in which the point falls, and/or by adding anew low propagation pathloss area to the existing low propagationpathloss areas of location-based propagation pathloss data.

Local controller 3320 may then execute the local trajectory algorithmusing the updated propagation pathloss data, such as by determining anupdated trajectory that increases the function of the optimizationcriteria (where the function of the optimization criteria isapproximated with the statistical model that is based on the updatedpropagation pathloss data). Mobile access nodes 3202 may then moveaccording to the updated trajectory while providing access to the servedterminal devices (e.g., by relaying data between the served terminaldevices and network access node 3208).

As the propagation pathloss data and the corresponding statistical modelis updated, the updated trajectory produced by the local trajectoryalgorithm may be different from the coarse trajectory. In some cases,the updated trajectory may yield an improved link strength. Inparticular, as mobile access node 3202 may have a more accuratecharacterization of the propagation pathloss along the outer surface ofindoor coverage area 3212, mobile access node 3202 may be able to moreaccurately determine an updated trajectory that has a strong link to theserved terminal devices through the outer surface.

In some aspects, local controller 3320 may additionally update theinitial routings to obtain updated routings, and then use the updatedroutings to control which served terminal devices that mobile accessnode 3202 provides access to. In various aspects, mobile access node3202 may also use predictable usage patterns in stage 3514 (e.g., in anymanner described above). This can include using predictable usagepatterns to determine scheduling and resource allocations and/or toselect fronthaul radio access technologies.

In some aspects, mobile access nodes 3202-3206 may repeat part of thisprocedure of message sequence chart 3500. For example, centraltrajectory controller 3210 may be configured to periodicallyre-determine new coarse trajectories, and to send the new coarsetrajectories to mobile access nodes 3202-3206. Mobile access nodes3202-3206 may then move according to the coarse trajectories andsubsequently update the new coarse trajectories to obtain updatedtrajectories. Mobile access nodes 3202-3206 may then provide access tothe served terminal devices while moving according to the updatedtrajectories.

As previously indicated, in some aspects mobile access nodes 3202-3206may determine their trajectories independent of a central trajectorycontroller. FIG. 36 shows exemplary message sequence chart 3600according to some aspects, which illustrates an example of this process.As shown in FIG. 36 , the served terminal devices may first connect tomobile access nodes 3202-3206 in stage 3602 a. This can include anyconnection procedure, such as a random access connection procedure.Mobile access nodes 3202-3206 may also connect to network access node3208 in stage 3602 a, and may therefore establish the wireless backhaullinks used by mobile access nodes 3202-3206 to relay user data betweenthe served terminal devices and network access node 3208.

Then, network access node 3208 may send mobile access nodes 3202-3206context information about indoor coverage area 3212 in stage 3604. Insome aspects, this context information can include, for example, mapdata for indoor coverage area 3212, or other information about theneighborhood environment. In some aspects, the context information caninclude propagation pathloss data, such as map-based propagationpathloss data or location-based propagation pathloss data. Networkaccess node 3208 may receive this context information from an externaldata network, such as a server that stores preconfigured contextinformation about indoor coverage area 3212. The context information cantherefore be predefined.

Mobile access nodes 3202-3206 may then determine coarse trajectories instage 3606. As mobile access nodes 3202-3206 are operating independentlyof a central trajectory controller, mobile access nodes 3202-3206 mayperform the processing previously described for stage 3504 for centraltrajectory controller 3210 in FIG. 35 . Accordingly, mobile access nodes3202-3206 may execute a local trajectory algorithm with their localcontrollers 3320 to determine coarse trajectories that increase, whichmay include maximizing, a function of an optimization criteria. Mobileaccess nodes 3202-3206 may use any type of trajectory-related processingdescribed above as part of the local trajectory algorithm.

In some aspects, mobile access nodes 3202-3206 may be configured to usea dual-phased optimization, such as where local controller 3320alternates between iteratively updating the coarse trajectory based onthe fronthaul in a first phase (e.g., to increase a function of theoptimization criteria that depends on the fronthaul but not thebackhaul) and updating the coarse trajectory based on the backhaul in asecond phase (e.g., to optimize a function dependent on the backhaul).

In some aspects, mobile access nodes 3202-3206 may use propagationpathloss data as part of the statistical model used for the localtrajectory algorithm. As noted above, in some aspects, network accessnode 3208 may transmit the propagation pathloss data as part of thecontext information in stage 3604. Local controller 3320 may receivethis propagation pathloss data (via baseband subsystem 3306) and save itfor execution of the local trajectory algorithm. In other aspects,network access node 3208 may transmit other context information aboutindoor coverage area 3212 as part of the context information in stage3604. In some aspects where network access node 3208 does not providethe propagation pathloss data, mobile access nodes 3202-3206 may beconfigured to locally generate the propagation pathloss data.

In an example using mobile access node 3202, mobile access node 3202 mayuse local learning subsystem 3318 to generate the propagation pathlossdata. In some aspects, local learning subsystem 3318 may use a same orsimilar technique to that described above for central learning subsystem3408 regarding stage 3504. For example, mobile access node 3202 maycollect radio measurements (e.g., provided as measurement reports by theserved terminal devices or network access node 3208, or locallydetermined by sensor 3322) at local learning subsystem 3318. Locallearning subsystem 3318 may then be configured to execute a propagationmodeling algorithm to determine the propagation pathloss data based onthe radio measurements (which can also be geotagged). This propagationpathloss data can be map-based propagation pathloss data orlocation-based propagation pathloss data. In some aspects where networkaccess node 3208 provides other context information about indoorcoverage area 3212, such as map data for indoor coverage area 3212,local learning subsystem 3318 may be configured to use the map data togenerate the location-based propagation pathloss data (e.g., by usingthe map data to plot the outer surface of indoor coverage area 3212, andtagging different points on the outer surface with propagation lossvalues or identifying different areas as low propagation pathlossareas).

In some aspects, one of mobile access nodes 3202-3206 may be configuredto generate the propagation pathloss data with its local learningsubsystem 3318, and then to send the propagation pathloss data to theother of mobile access nodes 3202-3206 (e.g., using their nodeinterfaces 3316). In some aspects mobile access nodes 3202-3206 may beconfigured to distribute the processing involved in the propagationmodeling algorithm amongst themselves, and to each execute a differentpart of the processing. Mobile access nodes 3202-3206 may then compilethe resulting data together the obtain the propagation pathloss data.

In some aspects, mobile access nodes 3202-3206 may also use predictableusage patterns (e.g., predicted user densities, predicted radioconditions, and/or predictable access usage) in stage 3606 as part ofthe statistical model used by the local trajectory algorithm. In someaspects, mobile access nodes 3202-3206 may also determine initialroutings, determine scheduling and resource allocations and/or selectfronthaul radio access technologies as part of stage 3606. This caninclude any related processing described above.

With reference back to FIG. 35 , after determining coarse trajectoriesin stage 3606, mobile access nodes 3202-3206 may perform datatransmission with the served terminal devices and network access node3208 in stages 3608 a-3608 b. Accordingly, mobile access nodes 3202-3206may provide access to the served terminal devices in indoor coveragearea 3212 by relaying data between the served terminal devices andnetwork access node 3208. Mobile access nodes 3202-3206 may follow theirrespective coarse trajectories while providing access to the servedterminal devices (e.g., where local controller 3320 provides the coarsetrajectory to movement controller 3328, which may then control steeringand movement machinery 3330 to move the mobile access node according tothe coarse trajectory).

As shown in FIG. 36 , the served terminal devices may report parametersback to mobile access nodes 3202-3206 in stage 3610. This can include,for example, where the served terminal devices provide radiomeasurements, current positions, and/or geotagged radio measurements. Insome aspects, mobile access nodes 3202-3206 may perform their own radiomeasurements with sensor 3322. These radio measurements, currentpositions, and geotagged radio measurements may form input data for thelocal trajectory algorithm.

Then, mobile access nodes 3202-3206 may then update the coarsetrajectories to obtain updated trajectories in stage 3612. In an exampleusing mobile access node 3202, local controller 3320 may update thestatistical model with the input data and then, using the updatedstatistical model, determine an updated trajectory for mobile accessnode 3202 that increases the function of the optimization criteria. Insome aspects, local learning subsystem 3318 may use the input data toupdate the propagation pathloss data, such as by using geotagged radiomeasurements to update propagation pathloss values for points on theouter surface and/or to identify or update low propagation pathlossareas. Local controller 3320 may then use this updated propagationpathloss data as part of the updated statistical model, and the updatedtrajectory may therefore be based on the updated propagation pathlossdata.

After updating their trajectories to obtain update trajectories in stage3612, mobile access nodes 3202-3206 may perform data transmission withthe served terminal devices in indoor coverage area 3212 and networkaccess node 3208 in stages 3614 a and 3614 b. Mobile access nodes3202-3206 may move according to their respective updated trajectorieswhile relaying data between the served terminal devices and networkaccess node 3208, and may therefore provide access to the servedterminal devices.

In some aspects, mobile access nodes 3202-3206 may repeat stages3610-3614 b, and may continue to receive parameters from the servedterminal devices, update their trajectories, and provide access to theserved terminal devices by relaying data between the served terminaldevices and network access node 3208. As the updated trajectories may bebased on propagation pathloss data that characterizes the propagationpathloss of indoor coverage area 3212, mobile access nodes 3202-3206 maybe able to use trajectories that yield strong links (e.g., with lowerpropagation pathloss and/or higher SNR) to the served terminal devices.Supported data rate and other link quality metrics may therefore beimproved.

In some aspects, mobile access nodes 3202-3206 may be configured toperform stage 3606 in coordination with each other. For example, mobileaccess nodes 3202-3206 may be able to cooperate to determine theircoarse trajectories. Instead of determining their individual coarsetrajectories independently, mobile access nodes 3202-3206 may thereforedetermine their coarse trajectories dependent on the coarse trajectoriesof each other.

For example, in some aspects mobile access nodes 3202-3206 may determinetheir coarse trajectories in stage 3506 in a sequential manner. Forexample, mobile access node 3202 may determine its coarse trajectoryfirst. Namely, local controller 3320 of mobile access node 3202 maydefine a function of an optimization criteria (e.g., related to asupported data rate or a link quality metric) and determine a coarsetrajectory for mobile access node 3202 that increases (e.g., maximizes)the function of the optimization criteria. The function of theoptimization criteria can be based on a statistical model of the radioenvironment around indoor coverage area 3212, which can use propagationpathloss data, other radio map data, radio measurements, positions ofserved terminal devices, and/or predictable usage patterns toapproximate the radio environment.

Then, after mobile access node 3202 has determined its coarsetrajectory, local controller 3320 may send the coarse trajectory tomobile access node 3204 (e.g., via node interface 3316 and basebandsubsystem 3306, which may use a device-to-device link to send thesignaling to mobile access node 3204). Local controller 3320 of mobileaccess node 3204 may then determine its own coarse trajectory whileconsidering the coarse trajectory of mobile access node 3202. Forexample, as part of the statistical model, local controller 3320 mayestimate the radio coverage provided to terminal devices in indoorcoverage area 3212 by mobile access node 3202 (e.g., by estimating thelink strength between mobile access node 3202 and different points inindoor coverage area 3212 while mobile access node 3202 follows itscoarse trajectory). Then, local controller 3320 may determine a coarsetrajectory for mobile access node 3204 that increases the function ofthe optimization criteria given the estimated radio coverage provided bymobile access node 3202 with its coarse trajectory.

Local controller 3320 of mobile access node 3204 may then send itscoarse trajectory and the coarse trajectory for mobile access node 3202to mobile access node 3206. Local controller 3320 of mobile access node3206 may then determine its own coarse trajectory using the coarsetrajectories of mobile access nodes 3204 and 3206 (e.g., by estimatingradio coverage provided by mobile access nodes 3204 and 3206 to indoorcoverage area 3212, and determining a coarse trajectory for mobileaccess node 3206 that increases a function of the optimization criteriagiven this estimated radio coverage). Mobile access nodes 3202-3206 maythen follow the coarse trajectories while relaying data between theserved terminal device and network access node 3208. Mobile access nodes3202-3206 may also receive parameters from the served terminal devices,update their trajectories (e.g., in coordination with each other asdescribed immediately above), and relay data while moving according tothe updated trajectories.

In some aspects, mobile access nodes 3202-3206 may be assigned todifferent geographic areas, and may be constrained to determinetrajectories within their respectively assigned geographic areas. Forexample, mobile access node 3202 may be assigned to a first geographicarea, mobile access node 3204 may be assigned to a second geographicarea, and mobile access node 3206 may be assigned to a third geographicarea. The geographic areas may be different (e.g., mutually exclusive,or without substantial overlap). Accordingly, when local controller 3320determines a trajectory (coarse or updated) for mobile access node 3202,local controller 3320 may be configured to determine a trajectory withinthe first geographic area that increases the function of theoptimization criteria. Accordingly, instead of determining a trajectorythat has no geographic bounds, local controller 3320 may be configuredto determine trajectories that are constrained by the first geographicarea assigned to mobile access node 3202. Mobile access nodes 3204 and3206 may similarly be configured to determine trajectories within theirrespectively assigned second and third geographic areas. In someaspects, mobile access nodes 3202-3206 may perform a negotiationprocedure (e.g., via signaling exchange executed by their localcontrollers 3320 with their cell interfaces 3314) to determine thegeographic areas assigned to each of mobile access nodes 3202-3206.

In some aspects, mobile access nodes 3202-3206 may be assigned to servedifferent geographic areas within indoor coverage area 3212. Forexample, mobile access node 3202 may be assigned to serve a firstgeographic area within indoor coverage area 3212, mobile access node3204 may be assigned to serve a second geographic area within indoorcoverage area 3212, and mobile access node 3206 may be assigned to servea third geographic area within indoor coverage area 3212. Using mobileaccess node 3202 as an example, local controller 3320 of mobile accessnode 3202 may be configured to determine trajectories that increase thefunction of the optimization criteria in the first geographic areawithin indoor coverage area 3212. Accordingly, mobile access nodes3202-3206 may be configured to determine trajectories that increase thefunction of the optimization criteria in their respectively assignedgeographic areas within indoor coverage area 3212.

In some aspects, mobile access nodes 3202-3206 may use the propagationpathloss data to control beamsteering directions for their antennasystems 3302. For example, by steering the antenna beams into indoorcoverage area 3212 through low propagation pathloss areas, mobile accessnodes 3202-3206 may improve link strength and consequently increase theoptimization criteria.

FIG. 37 shows an example using mobile access nodes 3202-3206 and indoorcoverage area 3212. As shown in FIG. 37 , mobile access nodes 3202-3206may steer their antenna beams 3702-3706 (e.g., directional radiationpatterns for transmission or reception that are steered and shaped bybeamsteering and/or beamforming) into indoor coverage area 3212 throughspecific areas of the outer surface of indoor coverage area 3212. In theexample shown in FIG. 37 , mobile access nodes 3202-3206 may steerantenna beams 3702-3706 through low propagation pathloss areas in theouter surface (e.g., openings 3212 a, 3212 e, and 3212 f). Accordingly,in some aspects mobile access nodes 3202-3206 may use beamsteeringdirections for antenna beams 3702-3706 that based on the propagationpathloss data. As the propagation pathloss data characterizespropagation pathloss through the outer surface, mobile access nodes3202-3206 may be able to use beamsteering directions that yield antennabeams that pass through the outer surface at low propagation pathlossareas.

In some aspects, central trajectory controller 3210 may be configured todetermine the beamsteering directions, and to provide the beamsteeringdirections to mobile access nodes 3202-3206. In these aspects,trajectory processor 3406 may be configured to determine thebeamsteering directions, such as part of the central trajectoryalgorithm executed in stage 3504 of message sequence chart 3500. Inother aspects, mobile access nodes 3202-3206 may be configured todetermine the beamsteering directions locally (e.g., independent of acentral trajectory controller). In these aspects, local controllers 3320of mobile access nodes 3202-3206 may be configured to determine thebeamsteering directions, such as part of the local trajectory algorithmexecuted in stage 3516 of message sequence chart 3500 or stages 3606 and3612 of message sequence chart 3600. Both options are explainedconcurrently below due to the similarities in the involved processing.

As introduced above, trajectory processor 3406/local controller 3320 maydetermine the beamsteering directions based on the propagation pathlossdata. For example, in cases where the propagation pathloss data ismap-based propagation pathloss data, trajectory processor 3406/localcontroller 3320 may be configured to define the function of theoptimization criteria as dependent on both trajectory and beamsteeringdirection (e.g., both trajectory and beamsteering directions unknownvariables that can be adjusted). As the statistical model (from whichthe function of the optimization criteria is derived) is based on thepropagation pathloss data, trajectory processor 3406/local controller3320 may determine a trajectory and beamsteering direction thatincreases the function of the optimization criteria in consideration ofthe propagation pathloss data.

In many cases, beamsteering directions that yield antenna beams passingthrough low propagation pathloss areas of the outer surface willincrease the function of the optimization criteria. For example, anantenna beam that passes through a low propagation pathloss area of theouter surface may yield a higher supported data and higher link qualitymetrics than an equivalent antenna beam that passes through a higherpropagation pathloss area of the outer surface. Accordingly, trajectoryprocessor 3406/local controller 3320 may determine beamsteeringdirections that yield antenna beams passing through low propagationpathloss areas of the outer surface, such as shown in FIG. 37 .

In cases where the propagation pathloss data is location-basedpropagation pathloss data (e.g., that identifies the positions of lowpropagation pathloss areas in the outer surface), trajectory processor3406/local controller 3320 may be configured to determine beamsteeringdirections that direct the antenna beams towards the low propagationpathloss areas identified in the propagation pathloss data. For example,in the case of mobile access node 3202, the propagation pathloss datamay specify that there is a low propagation pathloss area where opening3212 a is located (e.g., may specify coordinates that identify thelocation opening 3212 a). Accordingly, when selecting the beamsteeringdirection for mobile access node 3202, trajectory processor 3406/localcontroller 3320 may select a beamsteering direction that steers antennabeam 3702 through or towards opening 3212 a. This may likewise hold formobile access nodes 3204 and 3206 and openings 3212 e and 3212 f,respectively, as shown in FIG. 37 .

In aspects where central trajectory controller 3210 determines thebeamsteering directions, central trajectory controller 3210 may send thebeamsteering directions to mobile access nodes 3202-3206 (e.g., as partof stage 3506 in FIG. 35 ). Using mobile access node 3202 as an example,local controller 3320 may receive signaling that indicates thebeamsteering direction from central trajectory controller 3210, and thenprovide the beamsteering direction to baseband subsystem 3306. Inaspects where mobile access nodes 3202-3206 determine the beamsteeringdirections locally, their respective local controllers 3320 maydetermine the beamsteering directions and provide them to basebandsubsystem 3306.

After receiving the beamsteering directions, baseband subsystem 3306 mayperform transmission and reception using the beamsteering directions tocontrol beamsteering via antenna system 3302. This can include analog,digital, or hybrid beamsteering. In some aspects, trajectory processor3406 may update the beamsteering directions based on updated propagationpathloss data, and may send the beamsteering directions to mobile accessnodes 3202-3206. In some aspects, local controller 3320 of one or moreof mobile access nodes 3202-3206 may update the beamsteering directionsbased on updated propagation pathloss data.

In some aspects, such as in the case of FIG. 32 , there may be a fleetof mobile access nodes available to provide access to indoor coveragearea 3212. Depending on the current capacity at a given time, it may bepossible to provide access to the terminal devices in indoor coveragearea with only part of the fleet. For example, with reference to FIG. 32, if there is a smaller number of users in indoor coverage area 3212(e.g., during the day), it may be possible to effectively serve indoorcoverage area 3212 with only mobile access node 3202. As mobile accessnodes 3204 and 3206 are therefore not needed, they may be deactivated,such as by docking at a charging station to recharge for later use. Whenmore users are present in indoor coverage area 3212, mobile access node3204 and/or mobile access node 3206 may be reactivated (e.g., recalledfrom the charging stating) to help provide access to users in indoorcoverage area 3212.

In some aspects, central trajectory controller 3210 may also beconfigured to handle these decisions regarding the number of mobileaccess nodes from the fleet to deploy at a given time. For example,trajectory processor 3406 can be configured to determine a number ofmobile access nodes to deploy from a fleet at a given time, determinecoarse trajectories for the mobile access nodes, and then send signalingto the mobile access nodes that activates them and specifies the coarsetrajectories.

FIG. 38 shows exemplary message sequence chart 3800, which illustratesan example of this procedure according to some aspects. As shown in FIG.38 , central trajectory controller 3210 may be configured to estimatethe capacity requirements of indoor coverage area 3212 in stage 3802.Central trajectory controller 3210 may execute stage 3802 at trajectoryprocessor 3406. For example, trajectory processor 3406 may estimate thecapacity requirements of indoor coverage area 3212 based on the numberof served terminal devices in indoor coverage area 3212 and/or the datausage of the served terminal devices. For example, larger numbers ofserved terminal devices and/or the presence of served terminal devicesthat have high data usage can generally increase the capacityrequirements. Accordingly, when there are larger numbers of servedterminal devices and/or the presence of served terminal devices thathave high data usage, indoor coverage area 3212 may need radio accesslinks with high capacity to support the served terminal devices.

In some aspects, trajectory processor 3406 may estimate the capacityrequirements as a bandwidth requirement of indoor coverage area. Forexample, trajectory processor 3406 may use context information aboutindoor coverage area 3212 to estimate the bandwidth requirements forsupporting the served terminal devices in indoor coverage area 3212. Thecontext information can be, for example, information that indicates anumber of served terminal devices in indoor coverage area 3212 orinformation that indicates overall or individual data usage of theserved terminal devices. In some aspects, mobile access nodes 3202-3206and/or network access node 3208 may collect this context information(e.g., based on observations about the communication activity of theserved terminal devices) and report it to central trajectory controller3210. Trajectory processor 3406 may then use the context information todetermine the number of served terminal devices, the overall orindividual data usage of the served terminal devices, and subsequentlythe amount of bandwidth for supporting the data usage of the servedterminal devices. This determined amount of bandwidth can be thecapacity requirement.

In some aspects, trajectory processor 3406 may use predictable usagepatterns as part of the estimation in stage 3802. For example, centrallearning subsystem 3408 may have previously generated predictable usagepatterns for indoor coverage area 3212 related to predicted userdensities, predicted radio conditions, and/or predicted access usage.Trajectory processor 3406 may then use the predicted user densities,predicted radio conditions, and/or predicted access usage to estimatethe number of served terminal devices and/or the overall or individualdata usage of the served terminal devices. Trajectory processor 3406 maythen estimate the capacity requirements (e.g., amount of bandwidth)based on the estimated number of served terminal devices and/or theoverall or individual data usage of the served terminal devices.

In some aspects, trajectory processor 3406 may base the capacityrequirements on radio conditions of indoor coverage area 3212. Forexample, when radio conditions are strong, the radio links betweenmobile access nodes 3202-3206 may have higher SINR. This higher SINR mayin turn support higher data rates, and spectral usage of the availablebandwidth may therefore be more efficient. Accordingly, in some casesstrong radio conditions can reduce the capacity requirements (e.g.,reduce the amount of bandwidth to support the served terminal devices).Trajectory processor 3406 may therefore use radio measurements (e.g.,provided in the context information) and/or predicted radio conditions(e.g., part of the predictable usage patterns) to estimate the capacityrequirements of indoor coverage area 3212 in stage 3802, such as byscaling the capacity requirements depending on the current or predictedradio conditions (e.g., based on current or predicted SINR).

After estimating the capacity requirements of indoor coverage area 3212in stage 3802, trajectory processor 3406 may determine a number ofmobile access nodes to deploy based on the capacity requirements instage 3804. For example, if the capacity requirement is an amount ofbandwidth, trajectory processor 3406 may determine the number of mobileaccess nodes as a number of mobile access nodes that can provide theamount of bandwidth. In some cases, this can be a straightforwardcalculation, where a mobile access node is known to provide a certainamount of bandwidth and trajectory processor 3406 selects a number ofmobile access nodes that collectively provide the amount of bandwidth.

In some aspects, trajectory processor 3406 may also introduce aredundancy parameter into the determination of stage 3804. For example,as described above for FIGS. 26 and 27 , in some cases mobile accessnodes 3602-3208 may, for example, depart from their trajectories torecharge their power supplies. As this trajectory departure may divertmobile access nodes 3202-3206 from providing radio access to indoorcoverage area 3212, it can be advantageous to deploy additional mobileaccess nodes that can compensate for the trajectory departures ofrecharging mobile access nodes.

This redundancy parameter may therefore increase the number of mobileaccess nodes selected for deployment in stage 3804. For example, in someaspects trajectory processor 3406 may be configured to select oneadditional mobile access node than would otherwise be warranted forsupporting the capacity requirements (as estimated in stage 3802). Inother words, the redundancy parameter may specify a number of additionmobile access nodes to deploy, and may be equal to one (or,alternatively, another quantity). In other aspects, the redundancyparameter may be a percentage, and trajectory processor 3406 may beconfigured to scale the number of mobile access nodes (that couldsatisfy the capacity requirements) by the percentage to determine thenumber of mobile access nodes to deploy in stage 3804.

Central trajectory controller 3210 may then in stage 3806 activate thenumber of mobile access nodes determined in stage 3804. For example,trajectory processor 3406 may select mobile access nodes from the fleetof available mobile access nodes equal in quantity to the numberdetermined in stage 3804. Node interface 3402 of central trajectorycontroller 3210 may send signaling (via the radio access network towhich central trajectory controller 3210 interfaces) to the selectedmobile access nodes that instructs the selected mobile access nodes todeploy. In some aspects, central trajectory controller 3210 may alsodetermine coarse trajectories, initial routings, scheduling and resourceallocations, and/or fronthaul radio access technology selections for theselected mobile access nodes, and may also send these instructions instage 3806.

The selected mobile access nodes (e.g., one or more of mobile accessnodes 3202-3206) may then determine trajectories (e.g., coarse orupdated) that increase the function of the optimization criteria instage 3808 (e.g., at their respective local controllers 3320). Localcontrollers 3320 of the selected mobile access nodes may determine thesetrajectories in accordance with any technique described herein. Forexample, the optimization criteria may be a probability that thesupported data rate of the radio access connections of each of theserved terminal devices is above a threshold.

The selected mobile access nodes may then move according to thetrajectories while relaying data between the served terminal devices andnetwork access node 3208. In some aspects, the selected mobile accessnodes may attempt to solve the local coverage maximization problem instage 3810. This can include, at their local controllers 3320, updatingtheir trajectories to attempt to maximize the function of theoptimization criteria. In some aspects, local controllers 3320 can useparticle swarm optimization, or a technique described in E. Kalantraiet. al., “On the Number and 3D Placement of Drone Base Stations inWireless Cellular Networks.”

As previously described for FIGS. 26 and 27 , the selected mobile accessnodes may notify central trajectory controller 3210 and/or each otherwhen they depart from their trajectories for recharging. Their localcontrollers 3320 and/or trajectory processor 3406 of central trajectorycontroller 3210 may then determine updated trajectories for the otherselected mobile access nodes to compensate for the trajectory adjustmentof the recharging mobile access node.

In some aspects, central trajectory controller 3210 may be configured toupdate the selected mobile access nodes over time. For example,trajectory processor 3406 of central trajectory controller 3210 maycontinue to monitor the number of served terminal devices in indoorcoverage area 3212 and/or the overall or individual data usage of theserved terminal devices. Trajectory processor 3406 may then re-estimatethe capacity requirements of indoor coverage area 3212, and determine anupdated number of mobile access nodes to deploy based on the capacityrequirements. Trajectory processor 3406 may then activate additionalmobile access nodes and/or deactivate unneeded mobile access nodesdepending on if the updated number of mobile access nodes is greaterthan or less than the previous number of mobile access nodes.

FIG. 39 shows method 3900 of operating a central trajectory controller.As shown in FIG. 39 , method 3900 includes determining a coarsetrajectory for a mobile access node based on a function of a radio linkoptimization criteria (3902), wherein the function of the radio linkoptimization criteria is based on propagation pathloss data for an outersurface of an indoor coverage area and approximates a radio linkoptimization criteria for different coarse trajectories, and sending thecoarse trajectory to the mobile access node (3904).

FIG. 40 shows method 4000 of operating a mobile access node. As shown inFIG. 40 , method 4000 includes relaying data between a served terminaldevice in an indoor coverage area and a radio access network (4002),determining a trajectory based on a function of a radio linkoptimization criteria (4004), where the function of the radio linkoptimization criteria is based on propagation pathloss data for an outersurface of the indoor coverage area and approximates a radio linkoptimization criteria for different trajectories, and relaying databetween the served terminal device and the radio access network whenmoving the mobile access node according to the trajectory (4006).

FIG. 41 shows method 4100 of operating a mobile access node. As shown inFIG. 41 , method 4100 includes relaying data between a served terminaldevice in an indoor coverage area and a radio access network (4102),using a function of a radio link optimization criteria to determine atrajectory (4104), where the function of the radio link optimizationcriteria is based on surface propagation pathloss data of an outersurface of the indoor coverage area, and relaying data between theserved terminal device and the radio access network when moving themobile access node according to the trajectory (4106).

FIG. 42 shows method 4200 of operating a central trajectory controller.As shown in FIG. 42 , method 4200 includes estimating an amount ofbandwidth for supporting data usage by served terminal devices in anindoor coverage area (4202), determining a number of mobile access nodesto deploy to serve the indoor coverage area based on the amount ofbandwidth (4204), selecting one or more mobile access nodes based on thenumber (4206), and sending signaling to the one or more mobile accessnodes to activate the one or mobile access nodes (4208).

Function Virtualization with Virtual Networks of Terminal Devices

According to various aspects of this disclosure, groups of terminaldevices may establish their own virtual networks that support virtualequipment functions (VEFs). The terminal devices can collectively pooltogether their individual compute, storage, and network resources toform a hardware resource pool. A virtualization layer can then map theVEFs to the various resources of the hardware resource pool, and thevirtual network can thus execute the processing of the VEFs. In someaspects, the VEFs can be part of a larger processing function, where thecollective execution of the VEFs by the virtual network can realize theprocessing function.

FIG. 43 shows an exemplary network diagram according to some aspects. Asshown in FIG. 43 , terminal devices 4304-4312 may be configured to forma virtual network. Terminal devices 4304-4312 may then be configured touse this virtual network to execute various VEFs. As further describedbelow, these VEFs can be used for various different types of processing,including network offload processing, autonomous driving, sensing andmapping operations, and virtual cells. Terminal devices 4304-4312 canlogically allocate their individual compute, storage, and networkresources to form a hardware resource pool. The virtual network can thenuse the hardware resource pool to execute the VEFs.

FIG. 44 shows an exemplary internal configuration of terminal devices4304-4312 according to some aspects. As shown in FIG. 44 , terminaldevices 4304-4312 may include antenna system 4402, RF transceiver 4404,baseband modem 4406 (including digital signal processor 4408 andprotocol controller 4410), virtual network platform 4412 (includinginterface 4414 and function controller 4416), and resource platform 4418(including compute resources 4420, storage resources 4422, and networkresources 4424). Antenna system 4402, RF transceiver 4404, and basebandmodem 4406 may be configured in the manner of antenna system 202, RFtransceiver 204, and baseband modem 206 as shown and described forterminal device 102 in FIG. 2 .

Virtual network platform 4412 may be configured to handle communicationswith other terminal devices in the virtual network and to control thefunction virtualization operations of terminal devices 4304-4312.Resource platform 4418 may include the hardware resources of terminaldevices 4304-4312 that are provided for execution of VEFs by the virtualnetwork. As shown in FIG. 44 , virtual network platform 4412 may includeinterface 4414 and function controller 4416. Interface 4414 may be anapplication-layer processor (or software running on a processor) thatexchanges signaling with counterpart interfaces at other terminaldevices of the virtual network. Interface 4414 may therefore beconfigured to send signaling over a software-level logical connectionthat relies on baseband modem 4406 for wireless transmission at thelower layers. Interface 4414 may also exchange signaling with acounterpart interface at a function virtualization server that controlsthe function virtualization of the virtual network.

Function controller 4416 may be configured to control the functionvirtualization process. Accordingly, function controller 4416 may beconfigured to send and receive signaling through interface 4414,configure resource platform 4418 to perform VEFs, support avirtualization layer, and/or execute a VEF manager to allocate VEFs toother terminal devices.

Resource platform 4418 may include compute resources 4420, storageresources 4422, and network resources 4424. Compute resources 4420,storage resources 4422, and network resources 4424 may be the physicalhardware resources that are available for use in executing the VEFs. Forexample, in some aspects compute resources 4420 may include one or moreprocessors configured to retrieve and execute program code that definesthe operations of one or more VEFs in the form of executableinstructions. These processors can include any type of programmableprocessor (including FPGAs), and may be reprogrammable to load andexecute software for different VEFs. In some aspects, storage resources4422 may include one or more memory components that can store data forlater retrieval. Network resources 4424 may include the networkcommunication components of terminal devices 4304-4312. In some aspects,antenna system 4402, RF transceiver 4404, and baseband modem 4406 may belogically designated as part of network resources 4424, and thereforemay be available for use by VEFs running at resource platform 4418.

While compute resources 4420, storage resources 4422, and networkresources 4424 may physically be part of a given terminal device, theymay be logically allocated to the virtual network. The virtual networkmay therefore be able to assign compute resources 4420, storageresources 4422, and network resources 4424 (e.g., part or all) toperform VEFs, which can include executing an entire VEF locally at asingle terminal device or executing a VEF at multiple terminal devicesin a cooperative manner. These concepts are further described below.

FIG. 45 shows exemplary message sequence chart 4500 according to someaspects. According to various aspects, terminal devices 4304-4312 mayuse the process of FIG. 45 to form a virtual network and to subsequentlyuse the virtual network to execute VEFs. As shown in FIG. 45 , terminaldevices 4304-4312 may first form a virtual network in stage 4502. Insome aspects, this can include a predefined signaling exchange. Forexample, the respective interfaces 4414 of terminal devices 4304-4312may transmit and receive discovery signals (e.g., via their respectivebaseband modems 4406 using a device-to-device protocol) to detect andidentify nearby terminal devices. Respective interfaces 4414 of terminaldevices 4304-4312 may then establish signaling connections with eachother over which they can exchange signaling for communication purposes.

In some aspects, one of terminal devices 4304-4312 may act as a masterterminal device that exerts centralized control over the virtualnetwork. In the example of FIGS. 44 and 45 , terminal device 4304 mayassume this master terminal device role. In some aspects, terminaldevice 4304 may unilaterally assume the role of master terminal device(e.g., may initiate the formation of the virtual cell and assume themaster terminal device role), while in other aspects terminal devices4304-4312 may select a master terminal device as part of clusterformation in stage 4502.

As master terminal device, terminal device 4304 may be configured tocontrol the function virtualization. For example, its functioncontroller 4416 may be configured to execute a VEF manager that rendersdecisions regarding function virtualization for the virtual network. Thefunction controller 4416 of terminal device 4304 may then be configuredto send out signaling to the function controllers 4416 of terminaldevices 4306-4312 (via their interfaces 4414). This signaling mayinclude instructions which direct function controllers 4416 of terminaldevices 4306-4312 how to perform the function virtualization and toallocate VEFs to terminal devices 4306-4312 (e.g., to allocate VEFs forterminal devices 4306-4312 to perform on their respective resourceplatforms 4418).

As previously indicated, terminal devices 4304-4312 may be configured touse the virtual network to support execution of VEFs. In some aspects,the VEFs may be part of network offload processing. For example,terminal devices 4304-4312 may be configured to handle offloadprocessing for the radio access network (e.g., for one or more networkaccess nodes). This can include, for example, the protocol stackprocessing normally handled by network access nodes. The VEFs cantherefore correspond to various protocol stack processing functions. TheVEFs can additionally or alternatively be part of offload processing forthe core network (e.g., the core network behind the network accessnodes). The VEFs can therefore correspond to core network processingfunctions that are normally handled by core network servers.

In other aspects, the VEFs may be part of autonomous driving processing.For example, one or more of terminal devices 4304-4312 may be avehicular terminal device configured for autonomous driving. The VEFsmay therefore be any of the component functions involved in autonomousdriving (e.g., steering algorithms, image recognition, collisionavoidance, route planning, or any other autonomous driving function).

In other aspects, the VEFs can be part of sensing or mapping processing.For example, one or more of terminal devices 4304-4312 may be configuredto perform sensing functions (e.g., radio, image/video/audio,environmental). The VEFs can therefore be processing functions forprocessing the sensing data generated by these sensing functions. Inanother example, one or more of terminal devices 4304-4312 may beconfigured to perform mapping processing, such as to obtain image datato generate a 3D map. The VEFs can therefore be the processing functionsinvolved in processing the image data to generate the corresponding 3Dmap data.

The processing architecture of the virtual network formed by terminaldevices 4306-4312 is considered application-agnostic, and therefore theVEFs can be any type of processing functions. The use cases providedherein are therefore not limited to these specific examples.

As shown in FIG. 45 , terminal device 4304 (acting as the masterterminal device of the virtual network) may be configured to allocatethe VEFs to terminal devices 4306-4312 in stage 4504. For example,function controller 4416 of terminal device 4304 may first be configuredto select VEFs to allocate to terminal devices 4306-4312. As furtherdescribed below, function controller 4416 may perform this allocation byexecuting a VEF manager. In this example, there may be a plurality ofVEFs that form the overall processing for the virtual network. Functioncontroller 4416 of terminal device 4304 may therefore be configured toselect which of terminal devices 4306-4312 to assign each of theplurality of VEFs to. In some aspects, function controller 4416 may beconfigured to evaluate the available resources (e.g., of the respectiveresource platforms 4418 of terminal devices 4306-4312) of terminaldevices 4306-4312, and to allocate the VEFs based on these availableresources. For example, in some aspects, terminal devices 4304-4312 maypublish their resource capabilities as part of virtual network formationin stage 4502, which may inform the other terminal devices of theirresource capabilities (e.g., where terminal devices 4304-4312 havedifferent types of compute resources 4420, storage resources 4422,and/or network resources 4424, and may therefore have different resourcecapabilities). As their ability to execute VEFs may depend on theirrespective resource capabilities, function controller 4416 of terminaldevice 4304 may allocate VEFs to terminal devices 4306-4312 based ontheir respective resource capabilities (e.g., by identifying terminaldevices with resource capabilities that meet resource requirements ofparticular VEFs). In some aspects, function controller 4416 of terminaldevice 4304 may also assign VEFs to terminal device 4304, while in otheraspects function controller 4416 may not assign VEFs to terminal device4304.

When allocating the VEFs in stage 4504, function controller 4416 ofterminal device 4304 may send signaling to its peer function controllers4416 at terminal devices 4306-4312 that specify the VEFs that areallocated to terminal devices 4306-4312. Function controllers 4416 atterminal devices 4306-4312 may then configure their respective resourceplatforms 4418 to perform the allocated VEFs in stage 4506. Aspreviously indicated, the VEFs may be embodied as software that can beloaded and executed at compute resources 4420 that can also involvestorage and network operations provided by storage resources 4422 andnetwork resources 4424. In some aspects, function controller 4416 ofterminal device 4304 may send the software to terminal devices4306-4312, which their respective function controllers 4416 may receiveand load into compute resources 4420. In other aspects, software formultiple VEFs may be preinstalled onto compute resources 4420 ofterminal devices 4306-4312 (or preloaded onto a memory component ofterminal devices 4306-4312, such as in storage resources 4422). Uponreceiving the signaling from terminal device 4304 that specifies theallocated VEFs, function controllers 4416 of terminal devices 4306-4312may be configured to load the software for the respectively allocatedVEFs into compute resources 4420. This may therefore configure therespective resource platforms 4418 to perform the allocated VEFs.

As previously indicated, in some aspects terminal device 4304 may alsoallocate itself VEFs. Accordingly, as shown in FIG. 45 , functioncontroller 4416 of terminal device 4304 may also configure its resourceplatform 4418 to perform the allocated VEF in stage 4506 b.

As terminal device 4304 is acting as the master terminal device, itsfunction controller 4416 may be configured to oversee execution of theVEFs as part of the overall execution of the function virtualization.This can include controlling the parameters and timing of VEF executionand managing the exchange of input and result data of the VEF execution.Accordingly, as shown in FIG. 45 , function controller 4416 of terminaldevice 4304 may be configured to send an execute command to its peerfunction controllers 4416 at terminal devices 4306-4312 in stage 4508.The execute command may specify parameters that govern how terminaldevices 4306-4312 execute their respective VEFs. The execute command canadditionally or alternatively specify the timing at which terminaldevices 4306-4312 are to execute their respective VEFs. The executecommand can additionally or alternatively specify how input and resultdata of the VEF execution is to be exchanged between terminal devices4306-4312. For example, in some aspects the VEF allocated to one ofterminal devices 4306-4312 may use result data obtained by the VEF ofanother of terminal devices 4306-4312 as its input data. The result datacan be, for example, intermediate result data (e.g., the results ofcalculations of the VEF prior to its final conclusion) or output resultdata (e.g., the final result of calculations of the VEF). Accordingly,the result command may instruct terminal devices 4306-4312 where totransmit appropriate result data and/or where to receive appropriateinput data.

Terminal devices 4306-4312 may then receive the execute commands attheir respective function controllers 4416. Then, terminal devices4304-4312 may be configured to execute the VEFs with their respectiveresource platforms 4418 in stage 4510. For example, compute resources4420 at each of terminal devices 4304-4312 (or, alternatively,4306-4312) may be configured to execute the software for the VEF aspreviously configured in stages 4506 a and 4506 b. As previouslyindicated, this can include VEFs related to offload processing,autonomous driving, sensing or mapping, virtual cells, or VEFs relatedto other processing use cases. In some aspects, depending on the VEF,the involved VEF may also include operations by storage resources 4422and network resources 4424.

As referenced above, some VEFs may involve exchange of result data,which can be specified by terminal device 4304 in the execute command instage 4508. Accordingly, during the process of stage 4510, the VEFs atterminal devices 4304-4312 may be configured to exchange result data.For example, resource platform 4418 of one of terminal devices 4304-4312may identify the result data to be exchanged, and may then provide theresult data to the function controller 4416 of the terminal device. Thefunction controller 4416 may then transmit the result data to its peerfunction controller 4416 of another of terminal devices 4304-4312 (asspecified by the execute command; e.g., via their interfaces 4414). Thispeer function controller 4416 may then provide the result data to itscompute resources 4420, which may then use the result data as input datafor its VEF.

Terminal devices 4304-4312 may then finalize the output result data instage 4512. For example, the VEFs running at respective resourceplatforms 4418 of terminal devices 4306-4312 may be configured to sendthe output result data to their respective function controllers 4416.The function controllers 4416 of terminal devices 4306-4312 may thensend the output result data to terminal device 4304, where its functioncontroller 4416 may be configured to collect the output result data fromeach VEF. In some aspects, function controller 4416 of terminal device4304 may then finalize the output result data (e.g., collect oraggregate the output result data) to obtain the final data. In otheraspects, function controller 4416 of terminal device 4304 may thenprovide the output result data from the VEFs to the VEF running at itsown resource platform 4418. The VEF running at resource platform 4418 ofterminal device 4304 may then finalize the output result data to obtainthe final data for the VEFs. The final data can depend on the specifictypes of VEFs involved.

In some aspects, the virtual network of terminal devices 4304-4312 maybe configured to send the final data to an external location. Forexample, if the VEFs are for network offload processing for the radioaccess network, the virtual network may send the final data to one ormore network access nodes of the radio access network. In some aspects,function controller 4416 of terminal device 4304 (acting as the masterterminal device) may transmit this final data to the one or more networkaccess nodes, while in other aspects function controller 4416 ofterminal device 4304 may assign the function controller 4416 of one ormore of terminal devices 4306-4312 to transmit the final data (e.g., aspart of the execute command in stage 4508). The network access nodes maythen use the final data in place of performing their own networkprocessing. In another example where the VEFs are for network offloadprocessing for the core network, function controller 4416 of terminaldevice 4304 may transmit the final data to the relevant core networkservers, or may assign a function controller 4416 of one or more ofterminal devices 4306-4312 to transmit the final data to the relevantcore network servers. These core network servers may then use the finaldata in place of performing their own network processing.

In another example where the VEFs are related to autonomous driving, oneor more of terminal devices 4304-4312 may be vehicular terminal devicesconfigured for autonomous driving. Accordingly, function controller 4416of terminal device 4304 may send the final data (or may assign anotherof terminal devices 4306-4312 to send the final data) to these vehicularterminal devices, which can then use the final data to controlautonomous driving functionality (e.g., to influence driving and relateddecisions).

In another example where the VEFs are related to sensing or mappingfunctions, or another application where the final data is not usedwithin the radio access or core network, function controller 4416 ofterminal device 4304 may send the final data (or assign another ofterminal devices 4306-4312 to send the final data) to an externalserver. For example, function controller 4416 may send the final data tothe external server over an Internet connection (e.g., that uses theradio access connection provided by baseband modem 4406).

In some aspects, instead of designating one of terminal devices4304-4312 as a master terminal device, the virtual network composed ofterminal devices 4304-4312 may use a virtual master terminal device.FIG. 46 shows exemplary message sequence chart 4600 illustratingfunction virtualization according to some aspects. As shown in FIG. 46 ,terminal devices 4304-4312 may first form a virtual network in stage4602. Then, instead of designating one of terminal devices 4304-4312 asa master terminal device, terminal devices 4304-4312 may initializevirtual master terminal device 4614. For example, terminal devices4304-4312 may use function virtualization to run software that definesthe operation of a master terminal device. This can include, forexample, running a master terminal device VEF using the resourceplatform 4418 of multiple of terminal devices 4304-4312 that virtuallyrealizes a master terminal device. Accordingly, while virtual masterterminal device 4614 is executed virtually on multiple terminal devices,it may act as a separate logical entity.

In some aspects, the VEF that realizes virtual master terminal device4614 can be configured with the same or similar functionality asdescribed for function controller 4416 of terminal device 4304 whenacting as a master terminal device in the context of FIG. 45 .Accordingly, virtual master terminal device 4614 may perform stages4606-4614 in the same or similar manner as described for terminal device4304 and stages 4504-4512 in FIG. 45 .

FIG. 47 shows exemplary block diagram 4700 illustrating an examplelayout of this function virtualization according to some aspects. Asshown in FIG. 47 , block diagram 4700 is composed of three main blocks:VEFs 4702, VEF manager 4704, and VEF infrastructure 4706. VEFs 4702includes VEF 4702 a, VEF 4702 b, VEF 4702 c, and VEF 4702 d (in additionto one or more further VEFs). As previously described, VEFs 4702 may beprocessing functions that are virtualized by execution of software atresource platforms 4418 of terminal devices 4304-4312.

VEF manager 4704 may be a function that includes the overarching controllogic that manages allocation and execution of the VEFs. For example, aspreviously indicated VEF manager 4704 can be virtually realized byfunction controller 4416 of the master terminal device or virtual masterterminal device (e.g., terminal device 4304 or virtual master terminaldevice 4614).

VEF infrastructure 4706 may include the compute, storage, and networkresources that are logically allocated to the virtual network forexecuting the VEFs. Virtual compute 4708 may be the pool of computeelements collaboratively provided by terminal devices 4304-4312, virtualstorage 4710 may be the pool of storage elements collaborativelyprovided by terminal devices 4304-4312, and virtual network 4712 may bethe pool of network elements collaboratively provided by terminaldevices 4304-4312. Virtualization layer 4714 may be responsible formapping virtual compute 4618, virtual storage 4710, and virtual network4712 to the hardware compute resources 4716, hardware storage resources4718, and hardware network resources 4720 of terminal devices 4304-4312.In some aspects, virtualization layer 4714 may be virtually realized,for example, by function controller 4416 of the master terminal device(e.g., terminal device 4304) or by the virtual master terminal device(e.g., virtual master terminal device 4614). Hardware compute resources4716, hardware storage resources 4718, and hardware network resources4720 may correspond to the individual compute resources 4420, storageresources 4422, and network resources 4424 of terminal devices4304-4312.

As shown in FIG. 47 , hardware compute resources 4716 may be composed ofcompute elements 4716 a-4716 f. While the examples of FIGS. 43-46 aboveused terminal devices as the compute elements of the virtual network, insome aspects the virtual network may use other elements, including anyone or more of, for example, user equipment (laptops, tablets, desktopPCs, or other user equipment) and/or network equipment (e.g., small cellprocessing power, processing power in the cloud, or other networkequipment). These compute elements may therefore provide the computeresources to form the hardware compute resources 4716 with which thevirtual network actually executes the VEFs. The compute elements may beconfigured in the manner of terminal devices 4304-4312 as shown anddescribed in FIG. 44 , and may therefore have their own baseband modem4406, virtual network platform 4412, and resource platform 4418.

VEF manager 4704 (e.g., running at the controller of the master terminaldevice or at the virtual master terminal device) may be configured toallocate VEFs to compute elements 4716 a-4716 f (e.g., terminal devices4304-4312) in various different ways. FIG. 48 shows one example whereVEF manager 4704 may allocate VEFs to individual compute elements. Asshown in FIG. 48 , VEF manager 4704 may be configured to allocate VEF4702 a to compute element 4716 a, VEF 4702 b to compute element 4716 b,VEF 4702 c to compute element 4716 c, and VEF 4702 d to compute element4716 d. Accordingly, compute elements 4716 a, 4716 b, 4716 d, and 4716 emay be configured to execute VEFs 4702 a-4702 d at their respectiveresource platforms 4418.

Among other cases, this allocation can be applicable when computeelements 4716 a, 4716 b, 4716 d, and 4716 e have sufficient resources(e.g., compute, storage, and/or network, as applicable) at theirrespective resource platforms 4418 to execute an entire VEF. This maydepend on the requirements of the VEF, such as the amount of type ofinvolved computing, storage, and/or network operations. In other cases,one or more of the compute elements may not have sufficient resources toexecute an entire VEF. Accordingly, VEF manager 4704 may be configuredto allocate VEFs where some VEFs are distributed across multiple computeelements. FIG. 49 shows an example according to some aspects. As shownin FIG. 49 , VEF manager 4704 may be configured to allocate VEF 4702 ato compute elements 4716 a and 4716 b. This may result in VEF 4702 abeing virtually distributed across the respective resource platforms4418 of compute elements 4716 a and 4716 b. Accordingly, computeelements 4716 a and 4716 b may be configured to collaboratively executeVEF 4702 a.

FIG. 50 shows message sequence chart 5000 illustrating this procedureaccording to some aspects. As shown in FIG. 50 , compute elements 4716 aand 4716 b and VEF manager 4704 (e.g., running at a master terminaldevice or a virtual master terminal device) may form a virtual networkin stage 5002. VEF manager 4704 may then allocate VEFs to computeelements 4716 a and 4716 b in stages 5004 a and 5004 b. As described forFIG. 49 , VEF manager 4704 may allocate a single VEF (e.g., VEF 4702 a)to compute elements 4716 a and 4716 b. Compute elements 4716 a and 4716b may then configure their respective resource platforms 4418 to executethe VEF in stages 5006 a and 5006 b.

Then, VEF manager 4704 may send an execute command to compute elements4716 a and 4716 b in stages 5008 a and 5008 b. This can alternatively behandled by another element of the VEF architecture, such as byvirtualization layer 4714 (e.g., also running at a master terminaldevice or a virtual master terminal device).

Compute elements 4716 a and 4716 b may then execute the VEF in stage5010. As shown in FIG. 50 , stage 5010 may include stages 5012 a and5012 b and stage 5014. In stages 5012 a and 5012 b, compute elements4716 a and 4716 may locally execute the VEF at their respective resourceplatforms 4418. For example, compute element 4716 a may execute part ofthe overall VEF at its own resource platform 4418 while compute element4716 b executes another part of the overall VEF at its resource platform4418. Compute elements 4716 a and 4716 b may therefore execute the VEFin a distributed manner, where each executes a separate part of the VEF.Then, in stage 5014, compute elements 4716 a and 4716 b may exchangeresult data. This can be, for example, intermediate result data, wherethe VEF at one of compute elements 4716 a obtains intermediate resultdata that is used by the VEF at the other of compute elements 4716 b(and vice versa). Accordingly, compute elements 4716 a and 4716 b mayexchange such result data between their counterpart VEFs in stage 5014.Compute elements 4716 a and 4716 b can, for example, usedevice-to-device wireless links supported by their respective interfaces4414 (handling the software-level connection) and baseband modems 4406(handling the wireless transmission and reception via RF transceivers4404 and antenna systems 4402) to exchange the result data in stage5014. In some aspects, compute elements 4716 a and 4716 b may repeatstages 5012 a-5012 b and 5014, and may therefore repeatedly locallyexecute the VEF and exchange result data.

After execution of the VEF in stage 5010 is complete, compute elements4716 a and 4716 b may finalize the output result data of the VEF toobtain final data in stage 5016. This can include aggregating togetheroutput result data obtained from local execution of the VEF to obtainfinal data. If applicable, compute elements 4716 a and 4716 b may sendthe final data to the appropriate destination, such as to a radio accessor core network, autonomous driving systems, or a server for storingmapping or sensing data.

In some aspects, VEF manager 4704 may be configured to consider thewireless links between compute elements when allocating VEFs. Forexample, as described immediately above for FIG. 50 , when VEF manager4704 allocates a single VEF to multiple compute elements, the computeelements may exchange data with each other that is used to supportexecution of the VEF. Wireless exchange can also occur, for example,when separate VEFs at compute elements send result data to each other,such as in the case of stage 4510 as discussed above.

VEF manager 4704 may therefore be configured to perform a VEF allocationprocedure based on the wireless links. FIG. 51 shows exemplary decisionchart 5100 according to some aspects, which describes such a VEFallocation procedure. As VEF manager 4704 may be realized as software(e.g., running on a function controller of a master terminal device, orrunning as a virtual master terminal device on the resource platform ofmultiple compute elements), the logic of decision chart 5100 describedbelow can be embodied as executable instructions.

As shown in FIG. 51 , VEF manager 4704 may first be configured to obtainradio measurements for the wireless links between the compute elementsof the virtual network in stage 5102. For example, in the exemplary caseof FIG. 43 , the compute elements may be terminal devices 4304-4312. Thecompute elements may therefore perform radio measurements on wirelesssignals received from each other (e.g., with their respective basebandmodems 4406), and may then report the radio measurements to VEF manager4704.

After obtaining the radio measurements, VEF manager 4704 may evaluatethe wireless links based on the radio measurements in stage 5104. Forexample, VEF manager 4704 may be configured to evaluate the radiomeasurements to identify which compute elements have the highestperformance wireless links between them (e.g., have the highest signalstrength, signal quality, lowest noise or interference, lowest errorrate, or any other performance metric). In some aspects, VEF manager4704 may be configured to rank the wireless links, or to assign a metricto each wireless link (e.g., defined by a pair of compute elements) thatrepresents the performance of the wireless link.

Then, VEF manager 4704 may be configured to select compute elements forthe VEFs based on the evaluation in stage 5106. In some aspects, VEFmanager 4704 may examine the VEFs to determine how many wireless linksshould be used to support the VEFs. For example, from the plurality ofVEFs that form the overall processing of the virtual network, there maybe a subset of VEFs that would use multiple compute elements. This caninclude, for example, VEFs that are executed on multiple computeelements (e.g., as the involved processing is more than a single computeelement can support), or VEFs that use result data from othercounterpart VEFs. In some aspects, VEF manager 4704 may be configured toidentify a number of compute elements to support each of these VEFs. Insome aspects, VEF manager 4704 may be configured to compare the amountof involved processing resources for each VEF with the availableprocessing resources of the compute elements (e.g., of their respectiveresource platforms), and to determine a number of compute elements forexecuting the VEFs. Likewise, if a particular VEF uses result data fromone or more other VEFs (e.g., that are each executed on a differentcompute element), VEF manager 4704 may be configured to determine anumber of overall involved compute elements for the particular VEF(e.g., two if the particular VEF uses result data from one othercounterpart VEF). By using such evaluation, VEF manager 4704 may beconfigured to determine a number of compute elements involved insupporting each of the subset of VEFs.

Then, VEF manager 4704 may be configured to select compute elements foreach VEF in stage 5106. For VEFs that only use a single compute element,VEF manager 4704 may consider factors such as the available resources(e.g., at their respective resource platforms 4418) of the computeelements. For VEFs that use multiple compute elements (and thus involvewireless data exchange), VEF manager 4704 may additionally consider thewireless links between compute elements when selecting in stage 5106.For example, for a given VEF that is executed across a number of computeelements, VEF manager 4704 may be configured to select compute elements(equal in quantity to the number of compute elements) that have strongwireless links for the VEF. In an example with two compute elements, VEFmanager 4704 may be configured to select two of the available computeelements that have a strong wireless link (e.g., a radio measurement,relative distance, or other metric above a predefined threshold) for theVEF. VEF manager 4704 may similarly select available compute elementsfor VEFs that use more than two compute elements (e.g., selectingmultiple compute elements that have strong wireless links with eachother, or that form a sequence/chain of strong wireless links). Afterselecting the compute elements, VEF manager 4704 may then allocate theVEF to the compute elements in stage 5108).

For VEFs that use wireless data exchange to exchange result data withcounterpart VEFs, VEF manager 4704 may similarly identify computeelements (equal in number to the quantity involved in the VEF) that havestrong wireless links and assign the VEF and counterpart VEFs to thesecompute elements. For instance, in an example where a first VEF usesresult data from a second VEF, VEF manager 4704 may identify two computeelements that have a strong wireless link between them (e.g., asquantified by a distance between them or a radio measurement of thewireless link), and then select one of the compute elements for thefirst VEF and select the other compute element for the second VEF. Inanother example where a first VEF uses result data from a second VEF anda third VEF, VEF manager 4704 may identify a first compute element andtwo more compute elements that have strong wireless links with the firstcompute element. VEF manager 4702 may then select the first computeelement for the first VEF and the two more compute elements respectivelyfor the second and third VEFs. VEF manager 4704 may similarly selectcompute elements for VEFs that use different numbers of compute elementsfor wireless data exchange. After selecting the compute elements, VEFmanager 4704 may allocate the VEFs to the compute elements in stage5108.

In some cases, this allocation of VEFs based on wireless link strengthmay help to improve performance. For example, instead of blindlyallocating VEFs to compute elements, VEF manager 4704 may selectivelyallocate VEFs that use wireless data exchange to compute elements thathave wireless links well-suited to handle the wireless data exchange. Asstrong wireless links can yield higher data rates, higher reliability,and lower error, this can improve processing efficiency and computationspeed (as VEFs may be able to quickly exchange data as needed).

In some aspects, virtual networks may use VEFs to implement a virtualcell. For example, with reference to FIG. 43 , terminal devices4304-4312 may use the virtual network to virtually realize a cell usingvirtual cell VEFs. The virtual cell VEFs may therefore each be afunction of a standard cell that has been virtually embodied as a VEF.While the resulting virtual cell can provide similar or the same cellfunctionality of an actual cell in providing radio access to nearbyterminal devices, the underlying cell processing and radio activity canbe handled by terminal devices 4304-4312 in a distributed manner usingvirtual cell VEFs.

For example, standard cells can perform access stratum (AS) processingfor the radio access network. In the exemplary context of LTE, the ASprocessing can include Layers 1, 2, and 3 of the protocol stack, whichincludes, for example, the PHY, MAC, RLC, RRC, and PDCP entities. Theunderlying logic of this processing can therefore be embodied assoftware and virtually executed in a distributed manner as virtual cellVEFs by terminal devices 4304-4312. In addition to this cell processing,cells also perform radio activity to provide connectivity to nearbyterminal devices. This radio activity includes transmission of downlinkdata, reception of uplink data, and various other radio operations suchas transmission of reference signals and performance of radiomeasurements. Terminal devices 4304-4312 may also distribute this radioactivity amongst themselves, and may therefore perform equivalenttransmission, reception, and other radio operations with their ownnetwork resources.

FIG. 52 shows exemplary message sequence chart 5200 according to someaspects. Message sequence chart 5200 illustrates the procedure offorming and executing a virtual cell by distributing virtual cell VEFsbetween terminal devices forming a virtual network. As shown in FIG. 52, the procedure of message sequence chart 5200 may be handled by VEFmanager 4704. As previously indicated, VEF manager 4704 can be softwarerunning on a master terminal device (e.g., one of terminal devices4304-4312) or on a virtual master terminal device (e.g., that isvirtually realized by multiple of terminal devices 4304-4312).

Terminal devices 4304-4312 and VEF manager 4704 may first form a virtualcell in stage 5202. This procedure can be similar to the formation of avirtual network as previously described, where terminal devices4304-4312 exchange signaling to identify each other and establishwireless links for supporting the virtual cell. Then, VEF manager 4704may allocate VEFs to terminal devices 4304-4312 in stage 5204. Asindicated above, these VEFs can include the cell processing and radioactivity of a cell. For instance, in the exemplary case of an LTE cell,the LTE cell may execute downlink cell processing (e.g., AS processing)on downlink data and transmit the downlink data as downlink signals, andreceive uplink signals and execute uplink cell processing to obtainuplink data from the uplink signals. The LTE cell may also perform otherradio operations such as transmission of reference signals andperforming radio measurements. Cells of other radio access technologiesmay similarly perform such cell processing and radio activity.

This cell processing and radio activity can therefore be embodied asvirtual cell VEFs. For example, the cell processing for an LTE cell caninclude PHY, MAC, RLC, RRC, and PDCP processing. Each of these entitiesdefines a specific type of downlink and uplink processing to beperformed on downlink and uplink data. The cell processing involved inthese entities can therefore be virtualized as virtual cell VEFs, wherethe involved processing is embodied as executable instructions of thevirtual cell VEFs that define the logic of the processing entities. Aspreviously described, these virtual cell VEFs can be executing using,for example, compute resources 4420 of the resource platforms 4418 ofterminal devices 4304-4312.

The downlink and uplink transmission can also be virtualized as virtualcell VEFs that involve the use of the wireless components of terminaldevices 4304-4312, e.g., baseband modem 4406, RF transceiver 4404, andantenna system 4402. In some cases, these wireless components can belogically included as part of network resources 4424 of resourceplatform 4418, for example, where baseband modem 4406, RF transceiver4404, and antenna system 4402 are logically designated as part ofnetwork resources 4424 available for use in virtual cell VEFs.Accordingly, the virtual cell VEFs for radio activity can definewireless transmit and receive operations that use baseband modem 4406,RF transceiver 4404, and antenna system 4402 of terminal devices4304-4312.

In addition to these virtual cells VEFs related to cell radio activity,the virtual cell VEFs for radio activity can also include virtual cellVEFs for backhaul radio activity. In particular, standard cells may beconnected to a core network, such as via a wired connection. As terminaldevices 4304-4312 form a virtual cell, terminal devices 4304-4312 mayalso set up a wireless backhaul link to the radio access network (e.g.,to one or more nearby network access nodes). Terminal devices 4304-4312may then receive downlink data (e.g., destined to other terminal devicesserved by the virtual cell) from the radio access network over thewireless backhaul link, and may transmit uplink data (e.g., from otherterminal devices served by the virtual cell) to the radio access networkover the wireless backhaul link. The virtual cell VEFs for radioactivity may also include virtual cell VEFs that handle this wirelessbackhaul link.

These virtual cell VEFs for cell processing and radio activity maycollectively form a set of virtual cell VEFs, the combination of whichprovides the cell functionality of a standard cell. Accordingly, VEFmanager 4704 may allocate these virtual cell VEFs to terminal devices4304-4312 in stage 5204. In some aspects, VEF manager 4704 may allocatethe virtual cell VEFs based on the capabilities of the respectiveresource platforms 4418 of terminal devices 4304-4312. For example, VEFmanager 4704 may be configured to select terminal devices (or sets ofterminal devices) that can support high processing load on their computeresources 4420 for virtual cell VEFs that involve intensive processing.VEF manager 4704 may therefore be configured to allocate virtual cellVEFs based on the involved processing of the virtual cell VEFs and thesupported processing power of terminal devices 4304-4312. In anotherexample, VEF manager 4704 may be configured to allocate virtual cellVEFs based on the transmission or reception capabilities of terminaldevices 4304-4312. For example, some of the virtual cell VEFs mayinvolve radio activities, and therefore use wireless components toexecute. The transmission and reception capabilities of terminal devices4304-4312 may physically relate to their antenna systems 4402, RFtransceivers 4404, and baseband modems 4406, which may be virtuallyassigned for VEF uses as network resources 4424. VEF manager 4704 mayhave prior knowledge of the transmission and reception capabilities ofthe network resources 4424 of terminal devices 4304-4312, and maytherefore allocate virtual cell VEFs to terminal devices 4304-4312 basedon this prior knowledge of the transmission and reception capabilitiesof terminal devices 4304-4312

In some aspects, VEF manager 4704 may use the procedure of decisionchart 5100 to select terminal devices to allocate the virtual cell VEFsto. Accordingly, VEF manager 4704 may obtain radio measurements of thewireless links between terminal devices 4304-4312 (e.g., as locallyperformed by their respective baseband modems 4406 and reported by theirfunction controllers 4416), and then select terminal devices to assignto virtual cell VEFs that involve multiple terminal devices (e.g., toexecute or to wirelessly exchange result data with counterpart VEFs)based on the radio measurements.

Terminal devices 4304-4312 may then configure their respective resourceplatforms 4418 for the virtual cell VEFs in stage 5206. This caninclude, for example, receiving or downloading software that defines thevirtual cell VEFs, and loading the software into resource platforms4418. Then, VEF manager 4704 may send an execute command to terminaldevices 4304-4312 in stage 5208. Terminal devices 4304-4312 may receivethe execute command at their respective function controllers 4416 andproceed to execute the virtual cell VEFs to virtually realize a cell instage 5210. Stage 5210 can be a continuous process, where terminaldevices 4304-4312 continually execute their respectively allocatedvirtual cell VEFs to virtually realized the cell over time.

In some aspects, terminal devices 4304-4312 and VEF manager 4704 may beconfigured to repeat one or more of stages 5202-5210. For example, insome aspects VEF manager 4704 may be configured to re-allocate thevirtual cell VEFs, such as by selecting different terminal devices toallocate virtual cell VEFs to. In another example, VEF manager 4704 maybe configured to send another execute command that specifies differentparameters. This can therefore change execution of the virtual cell VEFsat terminal devices 4304-4312 without re-allocating the virtual cellVEFs.

FIG. 53 shows an exemplary network scenario illustrating a virtual cellaccording to some aspects. As shown in FIG. 53 , terminal devices4304-4312 may realize virtual cell 5302 by executing the correspondingvirtual cell VEFs. Virtual cell 5302 may therefore act as a virtual cellto provide radio access and connectivity to terminal devices 5306-5310.Accordingly, terminal devices 5306-5310 may be able to connect tovirtual cell 5302 as they would for a normal cell. For example, terminaldevices 4304-4312 may execute a synchronization signal VEF thattransmits synchronization signals for virtual cell 5302. Terminaldevices 5306-5310 may be able to receive and detect thesesynchronization signals, and then attempt to connect to virtual cell5302 using random access procedures. Virtual cell 5302 may then executea random access VEF that handles random access procedures for terminaldevices trying to connect to virtual cell 5302. After terminal devices5306-5310 connect to virtual cell 5302, virtual cell 5302 may thenprovide radio access to terminal devices 5306-5310 over fronthaul links5314 a-5314 c, over which virtual cell 5302 may transmit downlink datato terminal devices 5306-5310 and may receive uplink data from terminaldevices 5306-5310. Terminal devices 4304-4312 forming virtual cell 5302may perform cell processing on the downlink and uplink data using cellprocessing VEFs, and accordingly may virtually provide the functionalityof a cell.

Additionally, as virtual cell 5302 may in some cases not have a wiredconnection to the core network, virtual cell 5302 may use backhaul link5312 to connect with the core network and other external networks. Asshown in FIG. 53 , virtual cell 5302 may use backhaul link 5312 towirelessly interface with network access node 5304, which may in turnhave a wired connection to the core network. Virtual cell 5302 maytherefore relay uplink data (e.g., originating from terminal devices5306-5310) to network access node 5304 over backhaul link 5312, andnetwork access node 5304 may subsequently route the uplink data throughthe core network as appropriate (e.g., to a core network server, orthrough the core network to an external network). Likewise, in thedownlink direction, network access node 5304 may transmit downlink data(e.g., addressed to terminal devices 5306-5310) to virtual cell 5302over backhaul link 5312. Virtual cell 5302 may then relay the downlinkdata to terminal devices 5306-5310 as appropriate.

FIG. 54 shows an example illustrating allocation and execution ofvirtual cell VEFs at terminal devices 4304-4312 according to someaspects. As shown in FIG. 54 , terminal devices 4304-4312 may executeVEF manager 4704, which may exert primary control over virtual cell5302. While FIG. 54 shows VEF manager 4704 being executed by terminaldevices 4304-4312, in some aspects only one (e.g., a master terminaldevice) or only some of terminal devices 4304-4312 may execute VEFmanager 4704.

VEF manager 4704 may allocate virtual cell VEFs 5402-5418 to terminaldevices 4304-4312. In the example of FIG. 54 , virtual cell VEFs5402-5412 may be cell processing VEFs (as denoted by the light graycolor), while virtual cell VEFs 5414-5418 may be radio activity VEFs (asdenoted by the dark gray color). The number of virtual VEFs and thespecific allocation of virtual cell VEFs (including the distributionbetween multiple terminal devices) is exemplary and can be re-arrangedto any similar allocation.

Accordingly, terminal devices 4304-4312 may execute virtual cell VEFs5402-5418 using their respective resource platforms 4418, and in doingso may virtually realize a cell. In one example using LTE, virtual VEF5402 may be a PDCP VEF, virtual cell VEF 5404 may be an RLC VEF, virtualcell VEF 5406 may be an RRC VEF, virtual cell VEF 5408 may be a MAC VEF,virtual cell VEF 5410 may be a downlink PHY VEF, virtual cell VEF 5412may be an uplink PHY VEF, virtual cell VEF 5414 may be a downlinktransmission VEF, virtual cell VEF 5416 may be an uplink reception VEF,and virtual cell VEF 5418 may be a backhaul VEF. In various otherexamples, the various cell processing and radio activity functions of acell can be distributed amongst the terminal devices forming the virtualcell using VEFs. While the example of FIG. 54 maps protocol stack andphysical layer entities to virtual cell VEFs, this type of mapping isexemplary. Accordingly, in other aspects, specific subfunctions of theprotocol stack and physical layer entities can be realized anddistributed as an individual virtual cell VEFs. This concept is, forexample, discussed above with subfunctions such as random access VEFs.In another example, MAC scheduling could be realized as its own virtualcell VEF, while MAC header encapsulation could be realized as anothervirtual cell VEF. This same concept can be expanded, for example, to anysubfunction of a protocol stack or physical layer entity.

As previously indicated, in some aspects VEFs may wirelessly exchangedata with each other. FIG. 55 shows an example in which virtual cellVEFs 5402-5418 may exchange uplink and downlink data with each other.For example, virtual cell VEFs 5402-5418 may include various downlinkand/or uplink cell processing or radio activity functions. Accordingly,when one of virtual cell VEFs 5402-5418 finishes its processing onuplink or downlink data to obtain result data, it may send the resultdata to the next of virtual cell VEFs 5402-5418 along the processingpath. In an example using LTE layers, when MAC VEF 5408 finishesperforming MAC processing on downlink data to obtain result data (e.g.,a MAC Physical Data Unit (PDU)), it may provide the result data todownlink PHY VEF 5410. Downlink PHY VEF 5410 may then perform PHYprocessing on the result data to obtain its own result data, which itmay then send to downlink transmission VEF 5414. Downlink transmissionVEF 5414 may then transmit this data over the downlink paths offronthaul links 5314 a-5314 b. This same conceptual flow of informationapplies to the exchange of data between the various virtual cell VEFsshown in FIG. 55 . The processing paths shown in FIG. 55 are exemplary,and can be fit to any allocation of virtual cell VEFs.

As the virtual cell VEFs 5402-5418 are executed at various differentterminal devices, virtual cell VEFs 5402-5418 may use the wireless linksbetween terminal devices 4304-4312 to wirelessly exchange data asappropriate. For example, once MAC VEF 5408 (e.g., running virtually atthe resource platforms 4418 of terminal devices 4308-4312) obtains itsresult data in the downlink direction, it may wirelessly send the resultdata to downlink PHY VEF 4410 (e.g., running virtually at the resourceplatforms 4418 of terminal devices 4304 and 4306). For example, thefunction controller 4416 at one of terminal devices 4308-4312 maywirelessly send the result data (e.g., via its baseband modem 4406) tothe controller at one of terminal devices 4304 or 4306, which may thenprovide the result data to its resource platform 4418 for execution ofdownlink PHY VEF 4410. This can be handled at the virtualization layerrunning at the various function controller 4416 of terminal devices4304-4312. As previously described, virtual cell VEFs that run atmultiple terminal devices can similarly wirelessly exchange data asappropriate via their function controllers 4416 and baseband modems4406.

In some aspects, VEF manager 4704 may map certain terminal devices ofthe virtual cell to certain terminal devices served by the virtual cell.With reference to the example of FIG. 55 , VEF manager 4704 may allocatedownlink transmission VEF 5414 to terminal devices 4304 and 4306. Insome aspects, downlink transmission VEF 5414 may specify that terminaldevice 4304 performs downlink transmission for a first set of terminaldevices served by virtual cell 5302 and that terminal device 4306performs downlink transmission for a second set of terminal devicesserved by virtual cell 5302. Accordingly, when executing downlinktransmission VEF 5414, terminal devices 4304 and 4306 may split updownlink transmission by performing downlink transmissions to differentserved terminal devices.

This can also be implemented in the uplink direction where, for example,uplink reception VEF 5416 specifies that terminal device 4308 performsuplink reception for a first set of terminal devices served by virtualcell 5302 and that terminal device 4310 performs uplink reception for asecond set of terminal devices served by virtual cell 5302.

This allocation of certain terminal devices of the virtual cell tocertain terminal devices served by the virtual cell can also beimplemented for lower-layer processing. For example, downlinktransmission VEF 5414 and downlink PHY VEF 5410 may direct terminaldevice 4304 to perform lower-layer transmit processing (e.g., PHYprocessing, or PHY and MAC processing) and downlink transmission to afirst set of terminal devices served by virtual cell 5302, and may alsodirect terminal device 4306 to perform lower-layer transmit processing(e.g., PHY processing, or PHY and MAC processing) and downlinktransmission to a second set of terminal devices served by virtual cell5302.

Downlink PHY VEF 5410 running at terminal device 4304 may, for example,perform PHY processing on MAC packets (e.g., MAC PDUs provided by MACVEF 5408) addressed for the first set of terminal devices to produce PHYsymbols. Downlink transmission VEF 5414 running at terminal device 4304may then perform RF processing on the PHY symbols and then wirelesslytransmit the resulting RF signals to the first set of terminal devices.Downlink PHY VEF 5410 and downlink transmission VEF 5414 running atterminal device 4306 may similarly perform PHY processing and downlinktransmission for the second set of terminal devices.

In some aspects, uplink PHY VEF 5412 and/or uplink reception VEF 5416may similarly divide uplink PHY processing and/or uplink transmissionaccording to different sets of terminal devices served by virtual cell5302. For example, uplink reception VEF 5416 running at terminal device4308 may perform uplink reception for a first set of terminal deviceswhile uplink reception VEF 5416 running at terminal device 4310 mayperform uplink reception for a second set of terminal devices.Similarly, uplink PHY VEF 5412 running at terminal device 4308 mayperform uplink PHY processing for the first set of terminal deviceswhile uplink PHY VEF 5412 running at terminal device 4310 may performuplink PHY processing for the second set of terminal devices.

In some aspects, VEF manager 4704 may be configured to allocate thesesets of terminal devices to the terminal devices forming virtual cell5302 as part of the virtual cell VEF allocation process of stage 5202 inFIG. 52 . For example, in some aspects VEF manager 4704 may beconfigured to assign sets of served terminal devices to certain ofterminal devices 4304-4312 based on the position and/or wireless linksof terminal devices 4304-4312. For example, VEF manager 4704 may beconfigured to compare the positions of the served terminal devices(e.g., terminal devices 5306-5310) to the positions of terminal devices4304-4312, and to identify those of terminal devices 4304-4312 that areclose to each of terminal devices 5306-5310. Then, VEF manager 4704 maybe configured to allocate downlink transmission VEF 5414 and uplinktransmission VEF 5416 so terminal devices 4304-4312 perform downlink anduplink radio activity with those of terminal devices 5306-5310 that theyare close to. Additionally or alternatively, VEF manager 4704 may beconfigured to evaluate radio measurements that characterize the wirelesslinks between terminal devices 4304-4312 and terminal devices 5306-5310,and to allocate downlink transmission VEF 5414 and uplink transmissionVEF 5416 so terminal devices 4304-4312 perform downlink and uplink radioactivity with those of terminal devices 5306-5310 that they have strongwireless links with. In some cases, this can improve error rate, reduceretransmissions, and/or increase the supported data rate, as downlinkand uplink transmission may occur over strong wireless links.

In some aspects, downlink transmission, uplink reception, and downlinkand uplink PHY processing can be distributed between terminal devicesbased on radio resources. For example, in some aspects downlink PHY VEF5410 running at terminal device 4304 may perform downlink PHY processingfor a first set of time-frequency resources (e.g., resource elements(REs)) while downlink PHY VEF 5410 running at terminal device 4306 mayperform downlink PHY processing for a second set of time-frequencyresources. Downlink transmission VEF 5414 running at terminal device4304 may then perform downlink transmission for the first set oftime-frequency resources while downlink transmission VEF 5414 running atterminal device 4306 may perform downlink transmission for the secondset of time-frequency resources.

This distribution over radio resources can similarly be applied in theuplink direction. For example, uplink reception VEF 5416 running atterminal device 4308 may perform uplink reception for a first set oftime-frequency resources while uplink reception VEF 5416 running atterminal device 4310 may perform uplink reception for a second set oftime-frequency resources. Similarly, uplink PHY VEF 5412 running atterminal device 4308 may perform uplink PHY processing for the first setof time-frequency resources while uplink PHY VEF 5412 running atterminal device 4310 may perform uplink PHY processing for the secondset of time-frequency resources.

As previously indicated, in some aspects one of the virtual cell VEFsmay be a backhaul VEF. Backhaul VEF 5418 is one such example. BackhaulVEF 5418 can be executed by a single terminal device (e.g., terminaldevice 4312 in the example of FIG. 54 ), or can be distributed andexecuted virtually by multiple terminal devices. Backhaul VEF 5418 mayhandle transmission and reception over backhaul link 5312 of virtualcell 5302. For example, as denoted in FIG. 55 , in some aspects backhaulVEF 5418 may be configured to transmit uplink data (e.g., originatingfrom the served terminal devices of virtual cell 5302) to the radioaccess network (e.g., to network access node 5304), and to receivedownlink data (e.g., originating from the radio access network, corenetwork, or an external network, and addressed to the served terminaldevices of virtual cell 5302) from the radio access network. This caninclude using the wireless components (e.g., baseband modem 4406, RFtransceiver 4404, and antenna system 4402, which can be virtuallydesignated as network resources 4424) of the terminal devices executingbackhaul VEF 5418 to perform wireless transmission and reception.Accordingly, virtual cell 5302 may be able to maintain a backhaul linkto the core network via execution of backhaul VEF 5418. As shown in theexemplary processing flow of FIG. 55 , backhaul VEF 5418 may beconfigured to route received downlink data to the downstream virtualcell VEFs (e.g., that are configured to perform the next stage ofdownlink cell processing), and to receive uplink data from the upstreamvirtual cell VEFs (e.g., that are configured to perform the previousstages of uplink cell processing).

In some aspects, backhaul VEF 5418 may use downlink and/or uplinkaggregation. For example, with reference to the exemplary scenario ofFIG. 53 , virtual cell 5302 may serve multiple terminal devices5306-5310, and may maintain a backhaul link with network access node5304 (e.g., an anchor cell). In the downlink direction, network accessnode 5304 may be configured to identify different packets addressed toterminal devices 5306-5310 and to aggregate these component packetstogether to form an aggregated packet (e.g., that uses a single header,at a given network layer, for all of the component packets). Networkaccess node 5304 may then transmit the aggregated packet to virtual cell5302. Virtual cell 5302 (e.g., virtual cell VEFs 5402-5418 thatvirtually realize virtual cell 5302) may then separate the aggregatedpacket into the original component packets addressed to terminal devices5306-5310 and the transmit the component packets to terminal devices5306-5310. Additionally or alternatively, virtual cell 5302 maysimilarly use packet aggregation in the uplink direction. For example,virtual cell 5302 may receive multiple packets from terminal devices5306-5310, and aggregate these component packets together to form anaggregated packet (e.g., with a single header for all of the componentpackets). Virtual cell 5302 may then transmit the aggregated packet tonetwork access node 5304. In some cases, this use of aggregation canreduce overhead due to both the use of a single header for multiplecomponent packets and the reduced amount of control signaling (e.g.,scheduling requests/grants, buffer status reports, ACKs/NACKs, and othersignaling exchange that occurs on a per-packet basis).

In some aspects, the virtual cell VEFs allocated to virtual cell 5302may also include reference signal transmission VEFs and/or radiomeasurement VEFs. These virtual cell VEFs can similarly be allocated toone or more of the terminal devices forming virtual cell 5302.

In some aspects, the radio measurement VEFs may be distributed betweenmultiple terminal devices of virtual cell 5302. Then, as these terminaldevices are located at different positions, the radio measurement VEFcan use radio measurements obtained at different positions to estimatepropagation conditions. In one example, a master terminal device, suchas terminal device 4304, may be executing backhaul VEF 5418, and may nothave sufficient wireless component capabilities to concurrently performradio measurement. Accordingly, VEF manager 4704 running at terminaldevice 4304 may be configured to allocate a radio measurement VEF toanother terminal device of virtual cell 5302, such as terminal device4306. Terminal device 4306 may then execute the radio measurement VEF,and may perform and obtain radio measurements to report back to terminaldevice 4304. Terminal device 4304 can then use these radio measurementsinstead of performing its own radio measurements. This same concept canbe used in other cases where certain terminal devices in virtual cell5302 use radio measurements for various tasks but are occupied withother functionality (e.g., related to execution of their allocatedvirtual cell VEFs) to perform them. Accordingly, allocation of radiomeasurement VEFs to other terminal devices in virtual cell 5302 mayenable virtual cell 5302 to obtain these radio measurements by havingother terminal devices in virtual cell 5302 perform the radiomeasurements. In some aspects, the terminal devices in virtual cell 5302may perform a calibration procedure (which can be a calibration VEFassigned to the terminal devices by VEF manager 4704) in which theterminal devices of virtual cell 5302 compare their positions and/orlocally obtained radio measurements to identify which terminal deviceshave correlated propagation conditions (e.g., as they are locatedproximate to each other and/or have similar wireless links). VEF manager4704 may then be configured to assign terminal devices with correlatedpropagation conditions to perform radio measurements on behalf of eachother.

As previously indicated, in some aspects VEF manager 4704 may beexecuted by the function controller 4416 of a master terminal device,while in other aspects VEF manager 4704 may be executed by a virtualmaster terminal device (e.g., that is virtualized via distributedexecution of a master terminal device VEF at multiple terminal devicesof virtual cell 5302). VEF manager 4704 may assume primary control overthe operation of virtual cell 5302, including allocating virtual cellVEFs to the various terminal devices in virtual cell 5302. In someaspects where virtual cell 5302 has a master terminal device, the masterterminal device may be configured to execute backhaul VEF 5418. Themaster terminal device may therefore assume backhaul responsibilitiesfor virtual cell 5302.

In some aspects, creation and/or maintenance of virtual cells can bedynamic. For example, the creation of a virtual cell, such as in stage5202 in FIG. 52 , can be autonomous (ad-hoc) or network-triggered. Inthe case of autonomous creation, a triggering terminal device caninitial creation of the virtual cell. For example, one of terminaldevices 4304-4312 (that eventually form virtual cell 5302), such asterminal device 4304, may assume the role of the triggering terminaldevice. In one example, function controller 4416 of terminal device 4304may determine that a triggering condition has been met, and may thentrigger creation of a virtual cell. The triggering condition can be, forexample, detection of heavy network load (e.g., where functioncontroller 4416 of terminal device 4304 detects that network load and/oruser density exceeds a predefined threshold). In another example, thetriggering condition can be identification of an area that is poorlyserved by the radio access network (e.g., where function controller 4416of terminal device 4304 detects that local radio measurements in thearea are less than a predefined threshold).

After detecting that triggering condition is met, function controller4416 of terminal device 4304 may transmit a virtual cell create signal.For example, function controller 4416 may control baseband modem 4406 ofterminal device 4304 to transmit the virtual cell create signal, such asin the form of a wireless D2D signal (referring to any type of terminaldevice-to-terminal device signaling, including cellular as well as WiFiand Bluetooth, and not limited to any standard)). Other terminal devicesthat are configured to support virtual cells may monitor for suchvirtual cell create signals (e.g., by processing signals received attheir respective baseband modems 4406). For example, terminal devices4306-4312 may detect the virtual cell create signal at their respectivefunction controllers 4416, and may therefore determine that a virtualcell is being created. Terminal devices 4304-4312 may then exchangesignaling (e.g., via their respective function controllers 4416) to formthe virtual cell, thus completing stage 5202. In some aspects, thetriggering terminal device may assume the role of master terminal device(if applicable), while in other aspects the terminal devices maycollaboratively select a master terminal device (e.g., based on theprocessing and/or wireless communication capabilities of the terminaldevices, or based on the position of the terminal devices relative toother terminal devices).

In other cases, creation of a virtual cell can be network-triggered. Forexample, a network access node, such as network access node 5302, mayidentify that there is heavy network load or high user density, or thatthere is an area that has poor coverage. In some cases, network accessnode 5302 may then broadcast a virtual create cell signal, which one ormore of terminal devices 4304-4312 may receive and subsequently beginthe cell creation process previously described. In some cases, networkaccess node 5302 may identify a terminal device, such as terminal device4304, and send signaling to terminal device 4304 that instructs terminaldevice 4304 to create a virtual cell. In some cases, network access node5302 may identify the terminal devices that should form the virtualcell, such as terminal devices 4304-4312, and then send signaling toterminal devices 4304-4312 that instructs them to form a virtual cell.

In some aspects, when creating a virtual cell, the terminal devices mayexchange signaling with each other to determine the capabilities of theterminal devices. For example, when terminal devices 4304-4312 create avirtual cell and begin executing VEF manager 4704 (e.g., at a masterterminal device or at a virtual master terminal device), VEF manager4704 may receive signaling from terminal devices 4304-4312 thatspecifies the processing and/or communication capabilities of terminaldevices 4304-4312. In some aspects, the signaling can from terminaldevices 4304-4312 can also specify their positions and/or radiomeasurements that characterize wireless links between them. Aspreviously indicated, VEF manager 4704 may use the information in thissignaling to allocate virtual cell VEFs to terminal devices 4304-4312 instage 5204 of FIG. 52 .

In some aspects, virtual cell 5302 may be scalable. For example, VEFmanager 4704 may be configured to add or remove terminal devices fromvirtual cell 5302 based on the current load of virtual cell 5302. FIG.56 shows exemplary decision chart 5600 according to some aspects, whichillustrates an exemplary process of scaling virtual cell 5302. As shownin FIG. 56 , VEF manager 5602 may first evaluate the load on virtualcell 5302 in stage 5602. For example, the load can be measured in theamount of processing load (e.g., expressed as a percentage of themaximum processing load that the available virtual resources of virtualcell 5302 can handle), a data rate (e.g., the amount of uplink and/ordownlink data for its served terminal devices that passes throughvirtual cell 5302), a number of terminal devices served by virtual cell5302, or some other metric that quantifies the load on virtual cell5302. VEF manager 4704 may then compare the load to a threshold in stage5604 to determine whether the load is greater than the threshold. If theload is greater than the threshold, VEF manager 4704 may be configuredto add a terminal device (or multiple terminal devices) to virtual cell5302 in stage 5606. Conversely, if the load is not greater than thethreshold, VEF manager 4704 may be configured to remove a terminaldevice (or multiple terminal devices) from virtual cell 5302 in stage5608.

If VEF manager 4704 decides to add a terminal device to virtual cell5302, VEF manager 4704 may trigger transmission of a virtual cell invitesignal (e.g., by allocation of a virtual cell invite VEF to one of theterminal devices of virtual cell 5302, which may then transmit thevirtual cell invite signal via its baseband modem 4406). Nearby terminaldevices configured to support virtual cell functionality can then detectthe virtual cell invite signal, and their function controller 4416 canexchange signaling with VEF manager 4704 to arrange for the terminaldevice to join virtual cell 5302.

If VEF manager 4704 decides to remove a terminal device from virtualcell 5302, VEF manager 4704 may be configured to identify one of theterminal devices in virtual cell 5302, and to send the terminal device avirtual cell remove signal (e.g., by allocation of a virtual cell removeVEF to one of the terminal devices of virtual cell 5302, which may thentransmit the virtual cell remove signal via its baseband modem 4406).The terminal device may then leave virtual cell 5302, and may thereforecease performing any virtual cell VEFs for virtual cell 5302.

The ability to dynamically scale the size of virtual cell 5302 canenable virtual cell 5302 to adapt to its current load and to providesufficient resources to nearby terminal devices. Accordingly, when thereis high demand for virtual cell 5302 by nearby terminal devices, virtualcell 5302 can scale up in size to meet the demand. Conversely, whenthere is low demand for virtual cell 5302, virtual cell 5302 can scaledown in size.

In some aspects, virtual cell 5302 may additionally or alternatively beconfigured to split into multiple separate virtual cells. For example,in some aspects, VEF manager 4704 may be configured to trigger a virtualcell split, such as based on a triggering condition. This triggeringcondition can be, for example, detecting that a group of terminaldevices has moved away from the rest of the terminal devices in virtualcell 5302 (e.g., based on the current positions of virtual cell 5302).VEF manager 4704 may then, for example, identify a first set of terminaldevices in virtual cell 5302 to form a first virtual cell and identify asecond set of terminal devices in virtual cell 5302 to form a secondvirtual cell. VEF manager 4704 may then send out a virtual cell splitsignal to the first set of terminal devices and to the second set ofterminal devices that respectively assigns them to the first and secondvirtual cells. The first and second sets of terminal devices may thencreate the first and second virtual cells as assigned. This can include,for both the first and second virtual cells, exchanging signaling witheach other to form the virtual cells, initializing a new VEF manager,and allocating virtual cell VEFs to the terminal devices in the newfirst and second virtual cells.

In some aspects, virtual cell 5302 may additionally or alternatively beconfigured to merge with another virtual cell. For example, VEF manager4704 may detect that another virtual cell is proximate to virtual cell5302, and may decide to merge with the other virtual cell. Accordingly,VEF manager 4704 may exchange signaling with a counterpart VEF managerof the other virtual cell, and may arrange for the virtual cells tomerge. The terminal devices of virtual cell 5302 and the terminaldevices of the other virtual cell may then exchange signaling and formthe new merged cell, which can include initializing a new VEF managerfor the merged cell and allocating virtual cell VEFs to the terminaldevices in the merged cell.

In some aspects, virtual cell 5302 may be configured to coordinate withthe radio access network. For example, in some cases, served terminaldevices may handover from nearby network access nodes to virtual cell5302. As this may normally involve inter-cell signaling, virtual cell5302 may wirelessly exchange signaling directly from the nearby networkaccess node involved in the handover. Alternatively, virtual cell 5302may use backhaul link 5312 with network access node 5304 (e.g., theanchor cell), which may then forward the signaling to the network accessnods involved in the handover (e.g., using a network access node-networkaccess node interface). This can be handled by a mobility VEF that VEFmanager 4704 allocates amongst the terminal devices of virtual cell5302.

In some aspects, virtual cell 5302 may coordinate with the core networkto authenticate terminal devices that connect to it. For example, when aterminal device attempts to connect with virtual cell 5302, virtual cell5302 may verify the terminal device with the core network. In oneexample, virtual cell 5302 may execute a verification VEF, which maycommunicate with a subscriber database in the core network (e.g., usingbackhaul link 5312) to verify whether the terminal device is anauthorized user. Virtual cell 5302 may then permit the terminal deviceto connect if it is an authorized user, or may reject the terminaldevice if it is not an authorized user.

Virtual cell 5302 may also communicate with the radio access and/or corenetwork via backhaul link 5312 in various other scenarios. For example,virtual cell 5302 may be configured to communicate with the network whenit needs to update devices and get one from the network that is doingthe internal distribution by itself. In another example, virtual cell5302 may be configured to communicate with the core network or anotherexternal network to store result data (e.g., from execution of VEFs).

In various aspects, virtual cell 5302 may be either open or closed(e.g., permanently, or can switch between being either open or closed atany given time). For example, if virtual cell 5302 is open, any terminaldevice (or any authorized terminal device) may be permitted to joinvirtual cell 5302, or may be permitted to use virtual cell 5302 as aserved terminal device. If virtual cell 5302 is closed, only certainterminal devices may be permitted to join virtual cell 5302, or may bepermitted to use virtual cell 5302 as a served terminal device. In someaspects where virtual cell 5302 is a closed cell, virtual cell 5302 maybe configured to store authentication information that virtual cell 5302can use (e.g., as an authorization VEF) to determine which terminaldevices can join virtual cell 5302. In other aspects, virtual cell 5302may be configured to query a subscriber database in the core network toverify whether certain terminal devices are permitted to join virtualcell 5302.

In some aspects, virtual cells can be used to optimize handoverprocedures. Handover procedures can involve substantial signaling, andtherefore can contribute to network load. FIG. 57 shows an example inwhich the terminal devices of virtual cell 5302 are initially connectedto network access node 5702, and are moving together and in the samedirection. Rather than performing a time- and power-consuming handoverprocedure for each of the terminal devices to network access node 5704,virtual cell 5302 may perform a single handover procedure on behalf ofall of the terminal devices (e.g., handled by a handover VEF). In someaspects, virtual cell 5302 may alternatively perform multiple handoverprocedures to handover the terminal devices, where at least some of themultiple handover procedures handover multiple of the terminal devices.This can likewise save time and/or power, as at least some of thehandover procedures may handover multiple terminal devices in a singlehandover procedure.

Various examples described above refer to the use of backhaul link 5312and/or an anchor cell (e.g., network access node 5304). In some aspects,virtual cell 5302 may operate without any backhaul link or anchor cell,and may therefore act as an independent entity. Exemplary use casesinclude platooning, drone swarms, and local household networks, wherevirtual cell 4302 may coordinate communications between its servedterminal devices without transmitting or receiving external data via abackhaul link.

In some aspects, the backhaul link used by virtual cell 5302 may be anon-operator backhaul link (e.g., that falls outside of the domain ofthe mobile network operator). For example, in some aspects, virtual cell5302 may use a non-cellular radio access technology, such as WiFi orsatellite, for the backhaul link. For example, if one of terminaldevices 4304-4312, such as terminal device 4304, in virtual cell 5302supports WiFi or satellite communications, VEF manager 4704 may allocatea backhaul VEF to terminal device 4304. The backhaul VEF running onterminal device 4304 may therefore transmit and receive (e.g., using theWiFi or satellite wireless components of terminal device 4304 that arevirtually designated as network resources 4424) using a WiFi orsatellite backhaul link. In some aspects where non-operator backhaullinks are used, virtual cell 5302 may use additional authentication andsecurity features. For example, the backhaul VEF may establish a VPNwith the operator network, where the non-operator backhaul link formspart of the interface. Virtual cell 5302 and the operator network maythen exchange data over the VPN, which can protect the data.

In some aspects, virtual cell 5302 may be configured to implementdistributed relay functionality. For example, a group of terminaldevices may be located in a remote location, such as a group of standardterminal devices, vehicular terminal devices moving in a platoon, ordrones operating in a swarm in a remote location. As they are in aremote location, the terminal devices may not have traditional access tothe core network via cellular backhaul. Accordingly, the terminaldevices may form virtual cell 5302, which both these terminal devices aswell as other nearby terminal devices could use. If the terminal devicesneed to reach the core network and one of the terminal devices formingvirtual cell 5302 supports a long-range connection (e.g., has wirelesscomponents equipped with satellite capabilities), virtual cell 5302 mayuse this long-range connection to access the core network.

In some aspects, virtual cell 5302 may be configured to use machinelearning. For example, the terminal devices of virtual cell 5302 can usemachine learning to derive new filter coefficients for the machinelearning algorithm, and can the use the new filter coefficients amongstthemselves. For instance, the terminal devices can exchange the filtercoefficients with each other, such as in a split task setup wheredifferent terminal devices determine different filter coefficients andthen exchange the filter coefficients with each other. The terminaldevices can also send additional filter coefficients to the core networkfor storage, and can retrieve the filter coefficients at a later time(e.g., after reboot, or when a similar scenario occurs for which thestored filter coefficients are applicable).

In some aspects, the terminal devices of virtual cell 5302 may performtheir respective processing functions for executing the virtual cellVEFs with asynchronous processing. Accordingly, VEF manager 4704 mayallocate the virtual cell VEFs to the terminal devices so that thevirtual cell VEFs at each terminal device do not depend on virtual cellVEFs being executed at other terminal devices. This can enable theterminal devices to execute their virtual cell VEFs asynchronously.Additionally, virtual cell 5302 may use asynchronous processing to splitperformance requirements to different CPUs, and to run the CPUs ondifferent power values or thermal heat dissipation. Accordingly, theterminal devices can run their CPUs (for executing the virtual cellVEFs) with lower power values and/or with lower thermal heatdissipation.

In some cases, virtual cell functionality can be implemented withcompanion cells. These companion cells can be mobile cells that follow aparticular user or user group and provide access and other services tothe user or group. Groups of these companion cells can then form theirown virtual cell using the techniques described herein. Other virtualcells can also add companion cells as members.

In some aspects, credit or reimbursement may be provided to terminaldevices (e.g., to the user or customer that owns or uses the terminaldevice) in exchange for the participation of the terminal device in thevirtual cell. This credit or reimbursement can be provided, for example,by a network operator. The network operator can offer incentives ofgreater value in exchange for greater participation in the virtual cell.For example, terminal devices that act as master terminal devices canyield the highest incentives (e.g., to offset the higher powerconsumption associated with being the master terminal device). This canincentivize terminal devices to act as the master terminal device and/orto participate in the virtual cell.

These virtual cells can offer a wide array of advantages in differentscenarios. For example, the ability of virtual cells to dynamicallycreate may obviate the need to deploy permanent radio accessinfrastructure, which is costly to deploy and maintain. The scalablenature of virtual cells can also enable efficient resource usage.Furthermore, most conventional radio access infrastructure is stationarywhile virtual cells are mobile. Virtual cells can also shift maintenancecosts from the network operator to the users and customers.

Various exemplary uses of the proposed system can include stadiumevents, public meeting spaces, auditoriums, dense traffic settings(including platoons and convoys of vehicular terminal devices),factory/warehouse robots, and home and commercial private networks.Another example relates to an urban use case for cars where, forexample, vehicles in the city are not only their own device, but whenparked also constitute a small cell network that can provide access forpassing-by pedestrians and people living nearby.

FIG. 58 shows exemplary method 5800 of operating a terminal deviceaccording to some aspects. As shown in FIG. 58 , method 5800 includesreceiving an allocation of a virtualized function from virtual cell(5802), configuring a resource platform of the terminal device for thevirtualized function (5804), performing the virtualized function withthe resource platform to obtain result data (5806), and sending theresult data to another terminal device of the virtual cell (5808).

FIG. 59 shows exemplary method 5900 of operating a terminal deviceaccording to some aspects. As shown in FIG. 59 , method 5900 includesreceiving an allocation of a virtualized function from a virtual cell(5902), configuring a resource platform of the terminal device for thevirtualized function (5904), and executing the virtualized function toprovide a cell processing or radio activity function for a terminaldevice served by the virtual cell (5906).

FIG. 60 shows exemplary method 6000 of operating a terminal deviceaccording to some aspects. As shown in FIG. 60 , method 6000 includesexecuting a virtualized function manager for a virtual cell (6002),identifying a virtualized function that uses resources platforms ofmultiple terminal devices of the virtual cell (6004), identifying aplurality of terminal devices of the virtual cell based on wirelesslinks between the plurality of terminal devices (6006), and allocatingthe virtualized function to the plurality of terminal devices forexecution in a distributed manner (6008).

Virtual Cells Based on Geographic Regions

In some aspects, the virtual cells described above may be tied tospecific geographic regions. The virtual cells may use these geographicregions to control which terminal devices join and exit the virtual celland to define region-specific execution of virtual cell VEFs. Thesegeographic areas can be fixed (such as a virtual cell that is located inand serves a fixed geographic area) or dynamic (such as a mobile virtualcell that serves a moving area over time).

FIG. 61 shows an exemplary network scenario with virtual cell 6102according to some aspects. As shown in FIG. 61 , virtual cell 6102 mayinclude terminal devices 6104-6112. As previously described, virtualcell 6102 may virtually realize cell by allocating virtual cell VEFs toterminal devices 6104-6112, where the virtual cell VEFs define the cellprocessing and radio activity (e.g., cell functionality) of standardcells. Terminal devices 6104-6112 may then perform their respectivelyassigned virtual cell VEFs at their respective resource platforms 4418,and collectively may provide the cell functionality of a standard cellto nearby terminal devices. As shown in FIG. 61 , virtual cell 6102 mayinterface with internet/cloud network 6118 (e.g., via a radio access andcore network). Various other terminal devices 6114 and 6116 may alsointerface with internet/cloud network 6118.

FIG. 62 shows an exemplary internal configuration of terminal devices6104-6112. As shown in FIG. 62 , terminal devices 6104-6112 may includeantenna system 6202, RF transceiver 6204, baseband modem 6206, virtualnetwork platform 6212, and resource platform 6218. Components 6202-6224of terminal devices 6104-6112 may be configured in the same manner ascomponents 4402-4424 of terminal devices 4304-4312 as shown anddescribed for FIG. 44 . Function controllers 6216 may therefore controlthe virtual cell functions while resource platform 6218 may be allocatedto performing virtual cell VEFs as assigned.

Terminal devices 6104-6112 may also include position sensor 6226, whichcan be a component of virtual network platform 6212. Position sensor6226 may be any type of position sensor capable of determining aposition of the terminal device. In some aspects, position sensor 6226may be a geographic positional sensor, such as a sensor that usesgeographic satellite signals to determine positions (e.g., a GlobalNavigation Satellite System (GNSS) position sensor). In some aspects,position sensor 6226 may be a signal strength position sensor, such as ameasurement engine configured to perform signal strength measurements todetermine a relative distance between the terminal device and atransmitting device. As further described below, terminal devices6104-6112 may use their respective position sensors 6226 to determinetheir positions for use in the geographic-dependent functions of virtualcell 6102. In some aspects, terminal devices 6104-6112 may receive theirpositions from elsewhere outside of the terminal devices.

In some aspects, virtual cell 6102 may form based on a geographicregion. As denoted in FIG. 61 , terminal devices 6104-6112 may belocated within geographic region 6120. FIG. 63 shows exemplary flowchart 6300 illustrating formation of virtual cell 6102 according to someaspects. As shown in FIG. 63 , a triggering terminal device may firstcreate virtual cell 6102 and definite geographic region 6120 in stage6302. For example, one of terminal devices 6104-6112, such as terminaldevice 6104, may determine that a triggering condition is met (e.g.,network load above a threshold, or radio coverage level below athreshold), and may subsequently decide to create virtual cell 6102.

Terminal device 6104 may perform this action at its function controller6216 as shown in FIG. 62 . After deciding to create virtual cell 6102,function controller 6216 of terminal device 6104 may be configured todefine geographic region 6120 of virtual cell 6102. Geographic region6120 may be defined by a logical boundary that is subsequently used byvirtual cell 6102 to govern which terminal devices are invited to joinvirtual cell 6102 (e.g., to execute virtual cell VEFs as part of virtualcell 6102). In some aspects, function controller 6216 of terminal device6104 may use a predefined region as geographic region 6120. For example,function controller 6216 may be configured to use a predefined shape(e.g., a circle, square/rectangle, or other regular or irregular shape)as geographic region 6120. After defining geographic region 6120,function controller 6216 may locally store region data that definesgeographic region 6120. This region data can be, for example, a set ofcoordinates that define the boundaries of geographic region (e.g., thatdefine the outer perimeter, edges, and/or corners as geographiccoordinates). In some aspects, geographic region 6120 may be fixed, inwhich case the region data may be static (e.g., the actual geographicarea constituting geographic region 6120 may not change). In otheraspects, geographic region 6120 may be dynamic. For example, functioncontroller 6216 may define geographic region 6120 as a region relativeto terminal device 6104, such as a circle, square/rectangle, or othershape with terminal device 6104 positioned at the center (or any otherpoint within geographic region 6104).

Function controller 6216 of terminal device 6104 may then invite otherterminal devices within geographic region 6120 to join virtual cell 6102in stage 6304. In some aspects, function controller 6216 may transmit adiscovery signal (e.g., wirelessly via baseband modem 4406 of terminaldevice 6104), which nearby terminal devices may receive via theirbaseband modems and detect at their respective function controllers. Thediscovery signal may specify geographic region 6120 (e.g., may includethe region data that defines geographic region 6120). Terminal devices6106-6112 may therefore receive the discovery signal, and their positionsensors 6226 may determine their respective current position and providethe respective current positions to their respective functioncontrollers 6216. Function controllers 6216 may then use the region dataand current positions to determine whether terminal devices 6106-6112are within geographic region 6120. In an example using terminal device6106, position sensor 6226 of terminal device 6106 may determine thecurrent position of terminal device 6106 and provide the currentposition to function controller 6216. Function controller 6216 may thencompare the current position to the region data of geographic region6120 and determine whether terminal device 6106 is within geographicregion 6120. For example, if the current position is a geographicposition and the region data specifies a set of coordinates that definegeographic region 6120, function controller 6216 may determine whetherthe current position falls within the boundaries of geographic region6120 as defined by the set of coordinates. In another example, ifposition sensor 6226 is a measurement engine configured to perform asignal strength measurement, position sensor 6226 may perform a signalstrength measurement on the discovery signal transmitted by terminaldevice 6104 and determine a relative distance between terminal device6106 and terminal device 6104. If the region data specifies geographicregion 6120 by a distance (e.g., a distance from terminal device 6106,thus defining geographic region 6120 as a circle centered at terminaldevice 6106), function controller 6216 may then determine whether therelative distance between terminal devices 6106 and 6104 is less thanthe distance of the region data. If so, function controller 6216 maydetermine that terminal device 6106 is within geographic region 6120.

Terminal devices 6106-6112 may similarly perform this operation, and maydetermine that they are located within geographic region 6120. Functioncontrollers 6216 of terminal devices 6106-6112 may then transmit adiscovery response signal to terminal device 6104 that indicates thatterminal devices 6106-6112 are within geographic region 6120. Functioncontroller 6216 of terminal device 6104 may then invite terminal devices6106-6112 to join virtual cell 6102 in stage 6304, such as by exchangingfurther signaling with function controllers 6216 of terminal devices6106-6112 that invite terminal devices 6106-6112 to join virtual cell6102.

Other terminal devices, such as terminal devices 6114 and 6116, may alsoreceive the discovery signal from terminal device 6104. However, asshown in FIG. 61 , terminal devices 6114 and 6116, in some cases, maynot be located within geographic region 6120. Accordingly, when theirrespective function controllers 6216 evaluate the region data andcurrent positions, they may determine that terminal devices 6114 and6116 are not located within geographic region 6120. Therefore, in somecases, terminal devices 6114 and 6116 may not respond to the discoverysignal, and terminal device 6104 may not invite terminal devices 6114and 6116 to join virtual cell 6102

In a variation of the procedure described above for stages 6302 and6306, function controller 6216 of terminal device 6104 may transmit adiscovery signal in stage 6302 as part of creating virtual cell 6102.Function controllers 6216 of terminal devices 6106-6116 may receive thediscovery signal, and direct their position sensors 6226 to obtain therespective current positions of terminal devices 6106-6116. Functioncontrollers 6216 of terminal devices 6106-6116 may transmit a discoveryresponse signal to function controller 6216 of terminal device 6104 thatspecifies the current positions of terminal devices 6106-6116. Functioncontroller 6216 may then evaluate the region data for geographic region6120 and the respective current positions of terminal devices 6106-6116,and may determine whether terminal devices 6106-6116 are located withingeographic region 6120. Function controller 6216 of terminal device 6104may then invite the terminal devices that are within geographic region6120 to join virtual cell 6102 (e.g., by transmitting an invite signalto terminal devices 6106-6112) in stage 6306. Function controller 6216may not invite the terminal devices that are not in geographic region6120 (e.g., terminal devices 6114 and 6116) to join virtual cell 6102.

Terminal devices 6104-6112 may therefore create virtual cell 6102. Insome aspects, terminal device 6104 may assume the role of masterterminal device, and may therefore execute a VEF manager at its functioncontroller 6216 that manages the VEF execution of virtual cell 6102. Asshown in FIG. 63 , terminal devices 6104-6112 may publish their resourcecapabilities and exchange other information as applicable in stage 6306.For example, when terminal device 6104 is the master terminal device,function controllers 6216 of terminal devices 6106-6112 may sendsignaling to function controller 6216 of terminal device 6104 thatspecifies their resource capabilities. This can include the computingcapabilities of their respective compute resources 6220 (e.g.,processing power, such as expressed in floating points operations persecond (FLOPs) or another quantitative metric about computingcapabilities), storage capabilities of their respective storageresources 6222 (e.g., storage capacity, such as expressed in anybyte-based metric), and the network capabilities of their respectivenetwork resources 6224 (e.g., supported radio access technologies,supported transmit power, supported data rates, or any other metric thatquantities network or radio communication capabilities).

In other aspects, terminal devices 6104-6112 may select a masterterminal device. For example, while terminal device 6104 may act as thetriggering terminal device to initially create virtual cell 6102,terminal devices 6104-6112 may be configured to select a master terminaldevice after virtual cell 6102 is established. Accordingly, terminaldevices 6104-6112 may publish resource capabilities and exchange otherinformation in stage 6306, and then use their resource capabilities andother information to select a master terminal device. For example, therespective function controllers 6216 of terminal devices 6104-6112 maynegotiate with each other (e.g., via signaling exchange) to select,based on the respective resource capabilities, one of terminal devices6104-6112 to be the master terminal device. In some aspects, terminaldevices 6104-6112 may also exchange their current positions as part ofthe other information (e.g., as determined by their respective positionsensors 6226), and may use their current positions to select a masterterminal device. For example, terminal devices 6104-6112 may select aterminal device located in a central location relative to the otherterminal devices as the master terminal device.

In some aspects, terminal devices 6104-6112 may use a virtual masterterminal device, such as by executing a master terminal device VEF atthe resource platforms 6218 of multiple of terminal devices 6104-6112 ina distributed manner. Further references to master terminal devices invirtual cell 6102 can therefore refer to either of the cases where oneof terminal devices 6104-6112 is the master terminal device or wherevirtual cell 6102 uses a virtual master terminal device.

The master terminal device may then begin controlling operation ofvirtual cell 6102. For example, function controller 6216 of the masterterminal device may use the resource capabilities of terminal devices6104-6112 to allocate virtual cell VEFs (e.g., when running the VEFmanager). Terminal devices 6104-6112 may then execute the respectivelyallocated virtual cell VEFs in stage 6308 to virtually realize the cellfunctionality of a standard cell, thus providing access to servedterminal devices. Virtual cell 6102 can use any feature or functionalitypreviously described above, such as by allocating virtual cell VEFs forthe cell processing and radio activity for cells. Other terminal devicesnear virtual cell 6102 may therefore be able to use virtual cell 6102 inthe manner of a standard cell, such as by receiving downlink data andtransmitting uplink data.

Virtual cell 6102 may continue to use geographic region 6120 toinfluence virtual cell behavior. For example, in some aspects, terminaldevices that leave geographic region 6120 may leave virtual cell 6102 instage 6310 (e.g., cease participating in virtual cell VEF execution forvirtual cell 6102). The master terminal device may then re-allocate thevirtual cell VEFs previously allocated to these terminal devices. Insome aspects, the master terminal device may monitor the currentpositions of terminal devices 6104-6112 to determine whether they arestill located within geographic region 6120. For example, positionsensors 6226 of terminal devices 6104-6112 may periodically determinethe current positions of terminal devices 6104-6112, and functioncontrollers 6216 of terminal devices 6104-6112 may report theirrespective current positions to the master terminal device. Functioncontroller 6216 of the master terminal device may then determine whetherany of terminal devices 6104-6112 are not within geographic region 6120based on the region data. If so, function controller 6216 of the masterterminal device may transmit signaling to those of terminal devices6104-6112 that are not within geographic region 6120 to instruct them toleave virtual cell 6102. In some cases where geographic region 6120 isdynamic (e.g., changing over time), function controller 6216 of themaster terminal device may compare the current positions of terminaldevices 6104-6112 to the most recent region data for geographic region6120 to determine whether any of terminal devices 6104-6112 are notwithin geographic region 6120.

In some aspects, terminal devices 6104-6112 may periodically check todetermine whether they are still located within geographic region 6120.In some cases where geographic region 6120 is fixed, function controller6216 of terminal devices 6104-6112 may locally store the region data(e.g., after receiving the region data in a discovery signal from thetriggering terminal device). In some cases where geographic region 6120is dynamic, function controller 6216 of the master terminal device mayperiodically update the region data to reflect dynamic changes ingeographic region 6120. Function controller 6216 of the master terminaldevice may then send the region data to function controllers 6216 ofterminal devices 6104-6112, which may locally store it until the masterterminal device provides newer region data.

Position sensors 6226 of terminal devices 6104-6112 may thenperiodically determine the current positions of terminal devices6104-6112 and provide the current positions to the respective functioncontrollers 6216 of terminal devices 6104-6112. Function controllers6216 of terminal devices 6104-6112 may then compare their respectivecurrent positions to the region data to determine whether terminaldevices 6104-6112 are still within geographic region 6120. If, forexample, terminal device 6106 is not within geographic region 6120, itsfunction controller 6216 may transmit exit signaling to functioncontroller 6216 of the master terminal device. Terminal device 6106 maythen leave virtual cell 6102, and function controller 6216 mayre-allocate the virtual cell VEFs previously allocated to terminaldevice 6106.

As shown in FIG. 63 , stages of flow chart 6300 may repeat. For example,the master terminal device may repeat stage 6304 to invite new terminaldevices that enter geographic region 6120 to join virtual cell 6102. Forexample, function controller 6216 of the master terminal device (and,optionally, function controllers 6216 of one or more other terminaldevices in virtual cell 6102) may periodically transmit discoverysignals, which other nearby terminal devices may receive and identify attheir function controllers. The master terminal device and nearbyterminal device may then determine whether the nearby terminal device iswithin geographic region 6120 (e.g., using any technique describedabove). If so, the master terminal device may invite the nearby terminaldevice to join virtual cell 6102. Function processor 6216 of the masterterminal device may then, while running the VEF manager, allocatevirtual cell VEFs to the nearby terminal device.

While flow chart 6300 as described above shows aspects where terminaldevices leave virtual cell 6102 when they leave geographic region 6120,other aspects may use geographic region 6120 differently. For example,in some aspects, the triggering or master terminal device may inviteterminal devices within geographic region 6120 to join virtual cell6102, but may not instruct terminal devices that leave geographic region6120 to leave virtual cell 6120. For example, virtual cell 6102 mayinstruct terminal devices to leave virtual cell 6102 based on anothercriteria (e.g., other than geographic region), such as when theconnection between the terminal device and virtual cell 6120 fails (orwhen a signal strength or other criteria falls below a threshold).

In some aspects, virtual cell 6102 may use multiple geographic regions.FIG. 64 shows an exemplary scenario where virtual cell 6102 uses twogeographic regions according to some aspects. In the example of FIG. 64, virtual cell 6102 may use inner geographic region 6402 and outergeographic region 6404. Virtual cell 6102 may invite terminal devices tojoin virtual cell 6102 when the terminal devices enter inner geographicregion 6402, and may instruct terminal devices to leave virtual cell6102 when the terminal devices leave outer geographic region 6404.Accordingly, even if terminal device 6108 is part of virtual cell 6102and moves outside of inner geographic region 6402, terminal device 6108may only leave virtual cell 6102 when it leaves outer geographic region6404.

As previously indicated, when virtual cell 6102 is active, it mayprovide access to various served terminal devices in its vicinity. Theseserved terminal devices may be different from the terminal devices thatform virtual cell 6102, as they may not contribute their own resourcesto the virtual cell. The served terminal devices may connect to andinteract with virtual cell 6102 in a similar or same manner as to with astandard cell. The geographic regions that virtual cell 6102 uses tocontrol which terminal devices join and leave may be different from thearea in which served terminal devices can connect to virtual cell 6102.For example, virtual cell 6102 may provide access to an area larger thanits geographic regions (e.g., may serve a larger area than is used tocontrol which terminal devices join and leave virtual cell 6102).

FIG. 65 shows an exemplary diagram that illustrates the logicalarchitecture of virtual cell 6102 according to some aspects. As thisarchitecture is logical, various elements shown in FIG. 65 maycorrespond to other physical components (e.g., may be logical softwareentities that are executed by a physical processor). As shown in FIG. 65, virtual cell 6102 may include VEF manager 6502, which is previouslydetailed above for virtual cells in FIGS. 43-60 . As described above,VEF manager 6502 may be the logical control entity that managesoperation of the virtual cell VEFs. Accordingly, as shown in FIG. 65 ,VEF manager 6502 may include peer discovery 6506, location control 6504,and VEF allocation 6508.

Peer discovery 6506, location control 6504, and VEF allocation 6508 maybe subfunctions of VEF manager 6502, and may be configured as softwarefor execution on a processor. In some aspects, peer discovery 6506,location control 6504, and VEF allocation 6508 may be executed by amaster terminal device, such as a master terminal device that executespeer discovery 6506, location control 6504, and VEF allocation 6508 onits function controller 6216. In some aspects, the master terminaldevice may allocate some or all of the subfunctions of VEF manager 6502to other terminal devices in virtual cell 6102, which may then executethe allocated subfunctions on their respective resource platforms 6218(e.g., with compute resources 6220).

With initial reference to peer discovery 6506, peer discovery 6506 mayinclude functionality for discovering and adding new terminal devices tovirtual cell 6102. For example, as previously described, the terminaldevices in virtual cell 6102 may periodically transmit discoverysignals, which other nearby terminal devices may receive. In some caseswhere peer discovery 6506 is executed at the master terminal device,function controller 6216 of the master terminal device may controltransmission of discovery signals, reception of discovery responsesignals from a responding terminal device, and subsequent decisionsabout whether to add the responding terminal device to virtual cell6102. For example, when running peer discovery 6506, function controller6216 of the master terminal device may periodically trigger wirelesstransmission of the discovery signals (e.g., via baseband modem 6206 ofthe master terminal device), and may then use baseband modem 6206 tomonitor for reception of discovery response signals from a respondingterminal device. When a discovery response signal is received, functioncontroller 6216 may then decide whether to add the responding terminaldevice to virtual cell 6102. For example, the responding terminal devicemay include its current position in the discovery response signal, whichfunction controller 6216 of virtual cell 6102 may use to determinewhether the responding terminal device is within geographic area 6120and should be added to virtual cell 6102. In some cases, the discoveryresponse signal may include other information about the respondingterminal device, which function controller 6216 (e.g., running peerdiscovery 6506) of the master terminal device may use to determinewhether to add the responding terminal device to virtual cell 6102. Thiscan include, for example, using the other information to determinewhether the responding terminal device is a trusted device (e.g., basedon its manufacturer, or other identify information in its subscriberidentity).

In other cases, some or all of peer discovery 6506 may be executed atother terminal devices in virtual cell 6102. For example, the masterterminal device may assign other terminal devices to performtransmission of discovery signals and/or reception of discovery responsesignals. The function controllers 6216 of these terminal devices maythen use their respective baseband modems 6206 to perform thistransmission and reception, and to report back reception of discoveryresponse signals to the master terminal device (which can then decidewhether to add the responding terminal devices to virtual cell 6102 ornot). In some cases, the function controllers 6216 (e.g., running peerdiscovery 6506) of these terminal devices may also be configured todecide whether to add responding terminal devices to the virtual cell,such as by using any criteria described above for the master terminaldevice.

With reference to location control 6504, location control 6504 maymanage the monitoring of the locations of the terminal devices that formvirtual cell 6102. As shown in FIG. 65 , VEF manager 6502 may receivelocations 6512 as an input. Locations 6512 may include the positions ofthe terminal devices in virtual cell 6102 obtained by their respectiveposition sensors 6226. These current positions may then be used by VEFmanager 6502, including at location control 6504. In some cases wherelocation control 6504 is executed at the function controller 6216 of themaster terminal device, the other terminal devices in virtual cell 6102may be configured to periodically determine their current positions withtheir respective position sensors 6226 and to report their currentpositions to the master terminal device. Function controller 6216(running location control 6504) of the master terminal device may thenevaluate the current positions and the region data for geographic region6120 to determine whether the other terminal devices are still withingeographic region 6120. If function controller 6216 of the masterterminal device decides that a terminal device is not within geographicregion 6120, function controller 6216 of the master terminal device maytransmit exit signaling to the function controller of the other terminaldevice that instructs the other terminal device to exit virtual cell6102. In some cases where location control 6504 is executed at thefunction controllers 6216 of the other terminal devices of virtual cell6102, the function controllers 6216 of the other terminal devices mayreceive the current positions from their respective position sensors6226. The function controllers 6216 of these terminal devices may thenevaluate the current positions and region data of geographic region 6120to determine whether these terminal devices are still within geographicregion 6120. If not, the function controllers 6216 of these terminaldevices may transmit exit signaling to the function controller 6216 ofthe master terminal device that informs the master terminal device thatthey will exit virtual cell 6102.

With reference to VEF allocation 6508, VEF allocation 6508 may controlallocation of virtual cell VEFs to the terminal devices that formvirtual cell 6102. For example, function controller 6216 of the masterterminal device may be configured to execute VEF allocation 6508 and toconsequently allocate virtual cell VEFs to the other terminal devices.As previously described, in some aspects function controller 6216 (e.g.,running VEF allocation 6508) of the master terminal device may selectterminal devices to allocate virtual cell VEFs to based on therespective resource capabilities of the terminal devices that formvirtual cell 6102. Function controller 6216 may then send allocationsignaling to the function controllers 6216 of the other terminal devicesthat allocates the respectively selected virtual cell VEFs to the otherterminal devices.

As shown in FIG. 65 , virtual cell 6102 may use peer-to-peer (P2P)intra-cell communication 6510 to support communications between theterminal devices that form virtual cell 6102. Intra-cell communication6510 may refer to the logical signaling connections between the terminaldevices forming virtual cell 6102, where their respective interfaces6214 may form the lowest layer communications for the of the virtualcell application (e.g., handle the logical connections between theterminal devices for virtual cell purposes). The terminal devices maycontribute their wireless communication resources (antenna systems 6202,RF transceivers 6204, and baseband modems 6206) to intra-cellcommunication 6510. These wireless communication resources are shown inFIG. 65 as wireless communication resources 6532, which feeds intointra-cell communication 6510. Wireline communication resources 6530 mayinclude any wired communication connection used within virtual cell6102, such as those provided by supporting devices that execute supportVEFs 6526-6528 (as further described below).

The terminal devices forming virtual cell 6102 may use their respectiveantenna systems 6202, RF transceivers 6204, and baseband modems 6206 toprovide intra-cell communication 6510, where the respective interfaces6214 may form the lowest layer communications for the of the virtualcell application (e.g., handle the logical connections between theterminal devices for virtual cell purposes). The terminal devices invirtual cell 6102 may use intra-cell communication 6510 to exchangesignaling related to the virtual cells, such as discovery signaling anddiscovery response signaling, exit signaling, allocation signaling, andany other signaling related to the operation of the virtual cell.

Virtual cell 6102 may also use virtual cell VEFs 6514, which are alsodescribed above regarding FIGS. 43-60 . As previously described, virtualcell VEFs 6514 may be VEFs that realize the cell processing and/or radioactivity of cells, which can include downlink transmission, uplinkreception, other radio activity such as transmission of synchronizationsignals and radio measurement, and communication processing for radioaccess (e.g., AS processing). Virtual cell VEFs 6514 may be realized assoftware that defines computing, storage, and/or networking (e.g.,including wireless transmission and reception) operations. Accordingly,after being assigned virtual cell VEFs from VEF allocation 6508,terminal devices in virtual cell 6102 may execute the respectivelyallocated virtual cell VEFs at their resource platforms 6218.

As shown in FIG. 65 , execution of virtual cell VEFs 6514 may produceapplications and services 6524. Applications and services 6524 generallyrefers to the applications and services that virtual cell 6102 providesto its served terminal devices. For example, as previously described,nearby terminal devices may be able to use virtual cell 6102 for accessservices. Virtual cell 6102 may therefore provide a radio access networkavailable for nearby terminal devices to use to transmit and receiveuser data. In various exemplary cases, virtual cell 6102 may provideother applications and services as part of applications and services6524. For example, virtual cell 6102 may provide processing offloadservices, where its served terminal devices may offload processing tasksto virtual cell 6102. Virtual cell 6102 may then execute the processingtasks by embodying the processing tasks as virtual cell VEFs, andallocating the processing tasks to terminal devices forming virtual cell6102. The terminal devices may then execute the respectively allocatedvirtual cell VEFs to perform the processing task (e.g., using theircompute resources 6220), and provide result data back to the servedterminal devices. In another example, virtual cell 6102 may providestorage offload services, where its served terminal devices may providedata to virtual cell 6102 for storage and subsequent retrieval. Virtualcell 6102 may then provide the storage by allocating virtual cell VEFsto its terminal devices that specify storage of data (e.g., in storageresources 6222). The served terminal devices may then request the datafrom virtual cell 6102 at a later time, and virtual cell 6102 mayretrieve the data from the terminal devices on which it is stored andprovide the data back to the served terminal devices.

In some aspects, virtual cell 6102 may provide specialized applicationsand services as part of applications and services 6524. For example,virtual cell 6102 may provide offload processing related to autonomousdriving uses, where the served terminal devices may be autonomousvehicles that use virtual cell 6102 to process data related toautonomous driving. Virtual cell VEFs 6514 may therefore includeautonomous driving VEFs. In another example, virtual cell 6102 may, forexample, provide sensing or mapping functions as part of applicationsand services 6524. The served terminal devices may provide data tovirtual cell 6102, which virtual cell 6102 may use to generate sensingor other types of maps and store the resulting data.

In some aspects, virtual cell 6102 may use different types of virtualcell VEFs. For example, in the exemplary case of FIG. 65 , virtual cellVEFs 6514 may include remote VEFs 6516-6518 and core VEFs 6520-6522.Core VEFs 6520-6522 may have greater importance than remote VEFs6516-6518, and may therefore include the basic “core” functions thatvirtual cell 6102 supports at all or most times. Remote VEFs 6516-6518may therefore be other “auxiliary” functions that virtual cell 6102 maysupport at some times but not at others. For example, core VEFs6520-6522 may include cell functionality such as random access, backhaullinks, device scheduling and resource allocations, control of radioresources, device mobility, and any other functions that cells generallysupport. Virtual cell 6102 may treat these functions as core VEFs, andmay therefore generally allocate these VEFs to its terminal devices atmost or all times.

Remote VEFs 6516-6518 may include other optional functionalities, suchas offload processing, storage offload, support for special radio accesstechnologies, high-bandwidth or low-latency access, or any otherfunctionality that virtual cell 6102 can provide at some times but notat others. VEF allocation 6508 may be configured to determine whether ornot to allocate remote VEFs 6516-6518 at a given time. Accordingly, VEFallocation 6508 may be configured to selectively allocate one or more ofremote VEFs 6516-6518 at some times (thus providing the correspondingapplications and services to the served terminal devices of virtual cell6102) while not allocating the one or more of remote VEFs 6516-6518 atother times.

In some aspects where virtual cell 6102 uses this distinction betweenremote and core VEFs, VEF allocation 6508 may be configured to allocatevirtual cell VEFs to terminal devices based on context information ofthe terminal devices. For example, as core VEFs 6520-6522 may beconsidered more important to the functionality of virtual cell 6102, VEFallocation 6508 may be configured to allocate core VEFs 6520-6522 toterminal device of virtual cell 6102 that are expected to remain invirtual cell 6102 for an extended period of time. Accordingly, in somecases, the terminal devices in virtual cell 6102 may be configured toreport an expected duration to VEF allocation 6508 (e.g., via signalingexchange from their respective function controllers 6216), where theexpected duration is any indication about the amount of time that theterminal devices will remain in virtual cell 6102. The expecteddurations can be based on any type of higher-layer context information,such as past user behavior, programmed navigation routes, oruser-provided information. For example, VEF allocation 6508 may use pastuser movement behavior (e.g., data collected that details user movement)to estimate the duration of time that the user will remain in a givenlocation, and will thus be available as a resource for virtual cell6102. In another example, VEF allocation 6508 may obtain informationabout a current route that the user is traveling on, such as based ondata from a navigation app that has a user-programmed route. VEFallocation 6508 may use this information about the current route toestimate the duration of time that the user will remain close to virtualcell 6102. In another example, a user may be able to input informationto a terminal device that specifies their movement. VEF allocation 6508may then use this information to estimate the duration of time that theuser will remain close to virtual cell 6102.

Accordingly, VEF allocation 6508 may be configured to allocate remoteVEFs 6516-6518 and core VEFs 6520-6522 to the terminal devices invirtual cell 6102 based on these expected durations, such as byweighting allocation of core VEFs 6520-6522 to terminal devices thathave longer expected durations and weighting allocation of remote VEFs6516-6518 to terminal devices that have shorted expected durations.

In other cases, VEF allocation 6508 may be configured to track theamount of time that the terminal devices have been part of virtual cell6102. VEF allocation 6508 may then weight allocation of core VEFs6520-6522 to terminal devices that have been part of virtual cell 6102for longer periods of time, and weight allocation of remote VEFs6516-6518 to terminal devices that have been part of virtual cell 6102for shorter periods of time. For example, VEF allocation 6508 maylocally store a timestamp specifying when terminal devices in virtualcell 6102 joined virtual cell 6102 (e.g., at the time of creation ofvirtual cell 6102, or at a later time when a terminal device joinedvirtual cell 6102). VEF allocation 6508 may be configured to use thesetimestamps to determine how long terminal devices have been part ofvirtual cell 6102. In some aspects, VEF allocation 6508 may rank theterminal devices of virtual cell 6102 according to how long they havebeen part of virtual cell 6102, and may then allocate core VEFs6520-6522 to higher-ranked terminal devices and allocate remote VEFs6516-6518 to lower-ranked terminal devices.

In addition to the resources of terminal devices, in some aspectsvirtual cell 6102 may also be able to use resources of other nearbydevices. This can include base stations, access points, edge servers,and any other support device stationed in the vicinity of virtual cell6102 and make their compute, storage, and/or network resources availableto virtual cell 6102. Accordingly, virtual cell 6102 may be configuredto allocate support VEFs 6526-6528 to these supporting devices. Thesupporting devices may then execute support VEFs 6526-6528 with theirown respective compute, storage, and/or network resources. In somecases, the supporting devices may have greater compute, storage, and/ornetwork resources than the individual terminal devices of virtual cell6102. The supporting devices running support VEFs 6526-6528 may belogically considered part of virtual cell 6102, and may thereforecommunicate with the terminal devices in virtual cell 6102 usingintra-cell communication 6510. The supporting devices may thereforecontribute their own wireless resources (e.g., radio components of basestations and access points) as part of wireless communication resources6532. In some, the supporting devices may have wireline connections(e.g., wired interfaces between network access nodes), which they maycontribute as part of wireline communication resources 6530.

Some aspects described above use geographic regions to define the areain which terminal devices that form virtual cell 6102 are located. Insome aspects, virtual cell 6102 may additionally or alternatively usegeographic regions to define the coverage area of virtual cell 6102.FIG. 66 shows one example where virtual cell 6102 may divide itscoverage area 6602 into subareas 6602 a-6602 d. For example, VEFallocation 6508 (e.g., running at function controller 6216 of the masterterminal device, e.g., terminal device 6104) may allocate virtual cellVEFs for cell functionality in subarea 6602 a to terminal device 6108,allocate virtual cell VEFs for cell functionality in subarea 6602 b toterminal device 6106, allocate virtual cell VEFs for cell functionalityin subarea 6602 c to terminal device 6110, and allocate virtual cellVEFs for cell functionality in subarea 6602 d to terminal device 6112.

FIGS. 67 and 68 show two examples of virtual cell VEF allocations withinthe context of the example of FIG. 66 . As shown in FIG. 67 , masterterminal device 6104 may run VEF manager 6502, which may perform the VEFallocation. In particular, VEF manager 6502 may assign the entire cellfunctionality (e.g., all AS layers, including radio transmission andreception) for subarea 6602 a to terminal device 6108 (e.g., theterminal device assigned to that subarea), the entire cell functionalityfor subarea 6602 b to terminal device 6106, the entire cellfunctionality for subarea 6602 c to terminal device 6110, and the entirecell functionality for subarea 6602 d to terminal device 6112. This caninclude assigning virtual cell VEFs that make up the entire cellprocessing and radio activity for a given subarea to a single terminaldevice in virtual cell 6102. Terminal devices 6106-6112 may then act ascells and provide access service to served terminal devices within theirrespectively assigned subareas.

In the example of FIG. 68 , VEF manager 6502 may allocate virtual cellVEFs for radio activity and some lower-layer cell processing functions(e.g., PHY and MAC) respectively to terminal devices 6106-6112 for theircorresponding subareas. Accordingly, terminal devices 6106-6112 mayhandle radio activity and lower-layer cell processing functions locallyfor their assigned subareas, while the remaining cell processingfunctions are handled elsewhere. In the example shown in FIG. 68 , VEFmanager 6502 may allocate virtual cell VEFs for the remaining cellprocessing functions to terminal device 6104. This is exemplary, and invarious other aspects VEF manager 6502 may allocate virtual cell VEFsfor the remaining cell processing functions to other terminal devices invirtual cell 6102.

FIGS. 69-71 show additional examples of assignment of subareas andcorresponding virtual cell VEFs to terminal devices in virtual cell6102. As shown in FIG. 69 , VEF manager 6502 may logically dividecoverage area 6602 of virtual cell 6102 into subareas 6602 a and 6602 b.As shown in FIG. 70 VEF manager 6502 may then allocate virtual cell VEFsfor radio activity and lower-layer cell processing functions for subarea6602 a to terminal device 6106, and may allocate virtual cell VEFs forthe remaining cell processing functions for subarea 6602 a to terminaldevice 6108. Likewise, VEF manager 6502 may allocate virtual cell VEFsfor radio activity and lower-layer cell processing functions for subarea6602 b to terminal device 6112, and may allocate virtual cell VEFs forthe remaining cell processing functions for subarea 6602 b to terminaldevice 6110.

Alternatively, in the example of FIG. 71 , VEF manager 6502 may allocatevirtual cell VEFs for the entire cell functionality (radio activity andcell processing) for subarea 6802 a to terminal devices 6106 and 6108 toexecute in a distributed manner, and may allocate virtual cell VEFs forthe entire cell functionality for subarea 6802 b to terminal devices6110 and 6112 to execute in a distributed manner.

In some aspects, VEF allocation 6508 of VEF manager 6502 may use thecurrent positions of terminal devices 6106-6112 (e.g., provided as inputin the form of location 6512 in FIG. 65 ) to select which terminaldevices to assign to certain subareas of coverage area 6602 of virtualcell 6102. For example, VEF allocation 6508 may determine the currentpositions (e.g., most recently determined or reported positions) of theterminal devices currently in virtual cell 6102 (e.g., terminal devices6106-6112). In some cases, VEF allocation 6508 may first divide coveragearea 6602 of virtual cell 6102 into subareas (or, alternatively, thesubareas may be predefined, such any uniform division of coverage area6602 into subareas), and may then allocate virtual cell VEFs to terminaldevices 6106-6112 for the cell functionality in the subareas based onthe current positions of terminal devices 6106-6112. This can be, forexample, based on the proximity of terminal devices 6106-6112 to thesubareas.

In some aspects, VEF allocation 6508 may divide coverage area 6602 ofvirtual cell 6102 into subareas based on the current positions ofterminal devices 6106-6112. For example, VEF allocation 6508 maylogically divide coverage area 6602 into subareas that are locatedaround the current positions of terminal devices 6106-6112, and thenallocate virtual cell VEFs to terminal devices 6106-6112 for cellfunctionality in these resulting subareas.

In some aspects, virtual cell 6104 may provide mobility functionality toserved terminal devices as they move through different subareas ofcoverage area 6602. This mobility functionality may therefore enableserved terminal devices to handover to particular terminal devices invirtual cell 6102, where the handover can depend on the movement of theserved terminal devices and the specific subareas that the terminaldevices of virtual cell 6102 are assigned to. FIG. 72 shows an examplerelated to this mobility functionality according to some aspects. Asshown in FIG. 72 , coverage area 6602 may be divided into coverage areas6602 a-6602 (in the manner previously shown for FIG. 66 ), which may berespectively assigned to terminal devices 6108, 6106, 6110, and 6112.Served terminal device 7202 may be connected to virtual cell 6102, andmay initially be located in subarea 6602 c. Accordingly, terminal device6110 may provide access services to served terminal device 6110.

As shown in FIG. 72 , served terminal device 7202 may move from subarea6602 c to subarea 6602 a. As terminal device 6108 is assigned to subarea6602 a, terminal device 6108 may need to take over access services forserved terminal device 7202 (e.g., processing and transmission ofdownlink data, reception and processing of uplink data, paging, etc.).Accordingly, virtual cell 6102 may use a mobility layer to handle thesescenarios. FIG. 73 shows an example according to some aspects whereterminal devices 6104-6112 may execute mobility layer 7302. In someaspects, terminal devices 6104-6112 may execute mobility layer 7302 assoftware at their respective resource platforms 6218. For example,terminal devices 6104-6112 may each execute a local section of mobilitylayer 7302 at their respective resource platforms 6218, where the localsections of mobility layer 7302 may communicate with each other over alogical connection. As terminal devices 6104-6112 may execute mobilitylayer 7302 in a distributed manner, mobility layer 7302 may act as alogical connection between terminal devices 6104-6112, and may thereforeenable terminal devices 6104-6112 to negotiate mobility decisions forserved terminal devices.

In some aspects, virtual cell 6102 may use a procedure similar to ahandover for mobility between subareas of virtual cell 6102. Forexample, served terminal device 7202 may provide measurement reportsand/or position reports to terminal device 6110 during operation. Themeasurement reports may be based on measurements performed by servedterminal device 7202 on terminal device 6110 and/or other terminaldevices forming virtual cell 6102 (e.g., terminal devices 6104, 6106,6108, and 6112)

The local section of mobility layer 7302 running at terminal device 6110may evaluate the measurement reports and/or position and decide whetherserved terminal device 7202 should be transferred to another terminaldevice of virtual cell 6102 (e.g., as served terminal device 7202 hasmoved to another subarea). For example, if the measurement reports arebased on measurements by served terminal device 7202 of terminal device6110, and the measurement reports indicate weak measurements (e.g., lessthan a threshold), the local section of mobility layer 7302 running atterminal device 6110 may decide to transfer served terminal device 7202to another terminal device of virtual cell 6102. In some aspects, thelocal section of mobility layer 7302 at terminal device 6110 may thenrequest a position report from served terminal device 7202, and use theresulting position report to determine which subarea served terminaldevice 7202 is in.

In another example, served terminal device 7202 may be configured toperiodically send position reports to served terminal device 6110. Thelocal section of mobility layer 7302 at terminal device 6110 may thendetermine whether the current position of served terminal device 7202 iswithin subarea 6602 c and, if not, determine which subarea of coveragearea 6602 served terminal device 7202 is located in.

In the example of FIG. 72 , the local section of mobility layer 7302 atterminal device 6110 may determine that served terminal device 7202 islocated in subarea 6602 a. Accordingly, the local section of mobilitylayer 7302 at terminal device 6110 may communicate with the localsection of mobility layer 7302 at terminal device 6108 to arrange atransfer of served terminal device 7202 from terminal device 6110 toterminal device 6108. In some aspects, this can be a seamless procedure,where terminal device 6108 may be able to take over the access servicesfor served terminal device 7202 without an interruption and/or withoutextra signaling between served terminal device 7202 and virtual cell6102. In other aspects, access service for served terminal device 7202may be temporarily suspended and/or served terminal device 7202 mayexchange extra signaling with terminal devices 6110 and/or 6108 tofacilitate the transfer.

FIG. 74 shows exemplary method 7400 of operating a communication deviceaccording to some aspects. As shown in FIG. 74 , method 7400 includesdetermining that a triggering condition for creating a virtual cell ismet (7402), defining a geographic region for the virtual cell (7404),transmitting a discovery signal inviting nearby terminal devices to jointhe virtual cell based on the triggering condition being met (7406), anddetermining whether to accept one or more responding terminal devicesinto the virtual cell based on whether they are in the geographic region(7408).

FIG. 75 shows exemplary method 7500 of operating a communication deviceaccording to some aspects. As shown in FIG. 75 , method 7500 includesdetermining a current position of a first terminal device of a virtualcell (7502), determining whether the current position of the firstterminal device is within a geographic region for the virtual cell(7504), and after determining that the current position of the firstterminal device is outside of the geographic region, transmitting exitsignaling to the first terminal device that instructs the first terminaldevice to exit the virtual cell (7506).

FIG. 76 shows exemplary method 7600 of operating a communication deviceaccording to some aspects. As shown in FIG. 76 , method 7600 includesdetermining current positions of a plurality of terminal devices thatform a virtual cell (7602), wherein the virtual cell comprises acoverage area divided into multiple subareas, selecting a first terminaldevice of the plurality of terminal devices to assign to a first subareaof the multiple subareas (7604), and allocating, to the first terminaldevice, a first virtual cell virtualized function for providing cellfunctionality to served terminal devices of the virtual cell in thefirst subarea (7606).

FIG. 77 shows exemplary method 7700 of operating a communication deviceaccording to some aspects. As shown in FIG. 77 , method 7700 includesreceiving an allocation of a virtual cell virtualized function forproviding cell functionality to served terminal devices in a firstsubarea of a virtual cell (7702), and executing the virtual cellvirtualized function to provide the cell functionality to the servedterminal devices in the first subarea (7704).

FIG. 78 shows exemplary method 7800 of operating a communication deviceaccording to some aspects. As shown in FIG. 78 , method 7800 includesidentifying a plurality of virtual cell virtualized functions includingone or more first virtual cell virtualized functions of a first type andone or more second virtual cell virtualized functions of a second type(7802), selecting, from the plurality of virtual cell virtualizedfunctions, a selected virtual cell virtualized function of the first orsecond type based on an expected duration of time for a terminal deviceto remain in a virtual cell (7804), and allocating the selected virtualcell virtualized function to the terminal device (7806).

FIG. 79 shows exemplary method 7900 of operating a communication deviceaccording to some aspects. As shown in FIG. 79 , method 7900 includesidentifying a plurality of virtual cell virtualized functions includingone or more first virtual cell virtualized functions of a first type andone or more second virtual cell virtualized functions of a second type(7902), selecting, from the plurality of virtual cell virtualizedfunctions, a selected virtual cell virtualized function of the first orsecond type based on a duration of time a terminal device has been partof a virtual cell (7904), and allocating the selected virtual cellvirtualized function to the terminal device (7906).

Dynamic Local Server Processing Offload

Cloud servers can be used for both data storage and intensiveprocessing. When a local network, such as one comprised of Internet ofThings (I) devices, generates raw data, the local network may send theraw data to a cloud server (e.g., via an Internet backhaul link). Thecloud server may then process the raw data and subsequently store theresulting processed data. In some cases, a customer can then remotelyquery and access the processed data via the cloud server at a latertime, while in other cases the cloud server may send the processed databack to the local network for local use.

While such usage of cloud servers may offer greater storage andprocessing capacity compared to storage and processing at the localnetwork, the data transferred to and stored in the cloud sever may beconsiderable in size. Data transfer and storage costs can thereforebecome expensive for customers, in particular when considering thepotentially massive expansion of IoT device usage. Furthermore, when theprocessed data is used back at the local network, there may be a highlatency involved in the round-trip transfer of data to and from thecloud server.

Recognizing these issues with cloud server usage, various aspects ofthis disclosure provide methods and devices for dynamic local serverprocessing offload. As described below regarding various aspects of thisdynamic local server processing offload, a traffic filter can bepositioned along the user plane in the local network, and can beconfigured to filter the raw data generated at the local network toidentify certain target data. The traffic filter can then route thetarget data to a local server of the local network, which can thenprocess the target data and send the processed data to the cloud server.In some cases, the processed data can be smaller in size than the rawdata (e.g., due the compressive nature of the local processing), whichcan reduce the amount of data transferred to the cloud server overInternet backhaul. Additionally, in some aspects where the processeddata is used locally in the local network, the local server can provideit directly back to the appropriate devices in the local network, whichcan avoid the round-trip transfer to and from the cloud. The control ofthe offload filtering and processing can be controlled locally, such asby the local server, or externally, such as by the cloud server. Thecontrol of offload filtering and processing and can be based on variousdynamic parameters related to, for example, processing load, datatransfer costs, latency demands, and temperature of processingplatforms. The offload processing can also be dynamically scaled overtime based on changes in these dynamics parameters. The offloadprocessing can therefore adapt to varying conditions.

FIG. 80 shows an exemplary network diagram showing this dynamic localserver processing offload according to some aspects. As shown in FIG. 80, local network 8002 may interface with cloud network 8002 over backhaul8014. Local network 8002 may include various terminal devices 8004a-8004 f that may wirelessly connect to and communicate with networkaccess node 8006. Network access node 8006 may therefore provide a radioaccess network for terminal devices 8004 a-8004 f to transmit andreceive user and control plane data on. Network access node 8006 andterminal devices 8004 a-8004 f may be configured to use any type ofradio access technology, and accordingly may be configured to performphysical layer and protocol stack functions according to the appropriateradio access technology. In some aspects, terminal devices 8004 a-8004 fmay be configured in the manner shown for terminal device 102 in FIG. 2. In some aspects, network access node 8006 may be configured in themanner shown for network access node 110 in FIG. 3 .

Local network 8002 may also include control plane function (CPF) server8008, user-plane function (UPF) server 8012, and local server 8010. Asshown in FIG. 80 , network access node 8006 may interface with CPFserver 8008, UPF server 8012, and local server 8010 within local network8002. Network access node 8006 may transmit user data to cloud network8016 via UPF server 8012, which may perform routing functions on userdata (e.g., to route user data to the proper data network). UPF server8012 may transfer this user data to cloud network 8016 over backhaul8014. Cloud network 8016 may include various cloud servers, includingdata center 8018 and cloud servers 8020, 8022, and 8024. Data center8018 and cloud servers 8020-8024 may be configured to perform storageand processing functions, and in some aspects may interface with variousnetworks in addition to local network 8002.

In some aspects, local network 8002 may generate raw data for storage orprocessing. For example, terminal devices 8004 a-8004 f may generate rawdata including sensing data (e.g., temperature, humidity, camera/video,audio, image, or any other data generally used for monitoring, sensing,or surveillance purposes) and/or operational data (e.g., position,battery power, current task/route, diagnostic, or communication data).In some aspects, terminal devices 8004 a-8004 f may be IoT devicesconfigured to perform sensing in an operating area, such as IoT sensingdevices configured to generate temperature, humidity, camera/video,audio, image, radar, light, or any other similar type of data. These IoTdevices may also generate operational data that details their currentoperational status, including data that describes their position,battery power, current task/route, diagnostic status, currentcommunication status (e.g., current serving cell, active bearers,current data requirements and resource usage, current radio conditions),and past communication history (e.g., past serving cells, past datarequirements and resource usage, past radio conditions).

This sensing and operational data may be useful for various differentpurposes. One exemplary use case is a factory or warehouse setting whereterminal devices 8004 a-8004 f are robotic devices and/or sensingdevices. Accordingly, the raw data generated by terminal devices 8004a-8004 f can be processed to determine the current scenario in thefactory or warehouse, such as where certain objects are located (e.g.,objects stored in a warehouse, or parts used in an assembly line), whatthe current environment is (e.g., temperature), what the progress ofcertain tasks is (e.g., progress on loading a freight vehicle withobjects for transport, progress on building a device on an assemblyline), whether and where any errors are occurring, and other types ofinformation about the current scenario in the factory or warehouse.Other examples are described below.

As the raw data can be considerable in size, and therefor expensive totransfer to cloud network 8016 for processing, local network 8002 mayuse dynamic local server processing offload. Accordingly, local network8002 may have a traffic filter along the user plane (e.g., at networkaccess node 8006 or UPF server 8012), which can examine the raw datagenerated by terminal devices 8004 a-8104 f according to a filtertemplate. The traffic filter can then select a subset of the raw datathat matches the filter template, and can route this target data tolocal server 8010. Local server 8010 can then process the target datawith a processing function to obtain processed data. Depending on theparticular intended use of the processed data (e.g., what the processeddata is being used for, which can vary depending on the particular usecase), local server 8010 can then send the processed data back tovarious locations in local network 8002 (e.g., to terminal devices 8004a-8004 f, or to other devices operating in local network 8002, such asassembly machines or factory robots) for local use and/or can send theprocessed data to cloud network 8016. In some cases, this dynamic localserver processing offload can help to reduce latency, namely by avoidingthe round-trip to and from cloud network 8016 when the processed data isused locally. Furthermore, as in many cases the processed data issmaller in size than the raw data (due to the effects of processing),the dynamic local server processing offload can help to reduce theamount of data transferred to and/or stored in cloud network 8016. Thiscan in turn reduce cost and the processing load on the various cloudservers in cloud network 8016.

FIGS. 81-84 shows exemplary internal configurations of network accessnode 8006, local server 8010, UPF server 8012, and cloud server 8020according to some aspects. With initial reference to FIG. 81 , FIG. 81shows an exemplary internal configuration of network access node 8006according to some aspects. As shown in FIG. 81 , network access node8006 may include antenna system 8102, radio transceiver 8104, basebandsubsystem 8106 (including physical layer processor 8108 and controller8110), and application platform 8112 (including traffic filter 8114 andtemplate memory 8116). Antenna system 8102, radio transceiver 8104,baseband subsystem 8106 may be respectively configured in the mannerdescribed above for antenna system 302, radio transceiver 304, basebandsubsystem 306 of network access node 110 in FIG. 3 . Applicationplatform 8112 may be dedicated to the dynamic local server processingoffload, and may handle functions related to the filtering and routingof user plane data. As previously indicated, in some aspects networkaccess node 8010 may apply a traffic filter to user plane data (e.g.,generated by terminal devices 8004 a-8004 f) to select some of the userplane data that matches a filter template. Accordingly, traffic filter8114 may be a filter (e.g., a software filter) configured to tap userplane data (e.g., transport or application layer) passing throughnetwork access node 8010. Traffic filter 8114 may apply a filtertemplate stored in template memory 8116 to the user plane data to selectuser plane data that matches the filter template, and may then routethis target data accordingly. For example, traffic filter 8114 may beconfigured to perform packet inspection (e.g., Deep Packet Inspection(DPI)) on a stream of packets containing raw data, and to identify oneor more characteristics of each data packet (e.g., based on headerinformation). Traffic filter 8114 may then be configured to determinewhether any of the one or more characteristics of each data packet matchone or more parameters of the filter template (e.g., based on a 5-tupleor other filtering mechanism, as further described below). If so,traffic filter 8114 may classify the packet as target data, and routethe target data to local server 8010. If not, traffic filter 8114 mayclassify the packet as other data, and may route the other data alongits originally configured path (e.g., on an end-to-end bearer to cloudserver 8020).

FIG. 82 shows an exemplary internal configuration of local server 8010according to some aspects. As shown in FIG. 82 , local server 8010 mayinclude controller 8202, processing platform 8204, processing functionmemory 8206, and local storage 8208. Controller 8202 may be a processorconfigured to execute program code that defines the control logic oflocal server 8010, which can include instructing processing platform8204 to perform certain processing and handling communications withother network nodes. In some aspects, controller 8202 may also beconfigured to render decisions for the dynamic local server processingoffload, such as deciding on a processing offload configuration (asfurther described below).

Processing platform 8204 may include one or more processors configuredto perform processing functions (for example, the local processingfunctions as part of the dynamic local server processing offload). Insome aspects, processing platform 8204 may include one or more hardwareaccelerators configured with digital hardware logic to perform dedicatedprocessing tasks (where processing platform 8204 may hand off thesededicated processing tasks for execution by the hardware accelerators).Processing function memory 8206 may be a memory configured to store thesoftware for one or more processing functions, which processing platform8204 may retrieve and execute with its processing resources. Localstorage 8208 may be a memory configured to store various data, whichlocal server 8010 may retain for later access by other devices of localnetwork 8002.

FIG. 83 shows an exemplary internal configuration of UPF server 8012according to some aspects. As shown in FIG. 83 , UPF server 8012 mayinclude router 8302, traffic filter 8304, and template memory 8306. Aspreviously indicated, UPF server 8012 may be positioned on the userplane between network access node 8010 and backhaul 8014, and may beresponsible for routing user plane data along the appropriate routingpaths (e.g., according to the configured bearers for the user planedata). Router 8302 may be configured to handle this routingfunctionality. Traffic filter 8304 may be configured to tap user planedata passing through UPF server 8012 and to apply a filter templatestored in template memory 8306 to the user plane data. Traffic filter8304 may select the user plane data that matches the filter template(for example, using the parameter-based process described above fortraffic filter 8114) as target data, and may then route the target datato local server 8010 while routing other data along its originallyconfigured path (for example, to cloud server 8020).

FIG. 84 shows an exemplary internal configuration of cloud server 8020according to some aspects. As shown in FIG. 84 , cloud server 8020 mayinclude controller 8402, processing platform 8404, processing functionmemory 8406, and cloud storage 8408. Controller 8402 may be a processorconfigured to execute program code that defines the control logic ofcloud server 8020, including deciding which processing to perform atprocessing platform 8404 and handling communications with other networknodes. In some aspects, controller 8402 may be configured to renderdecisions for the dynamic server processing offload, such as deciding ona processing offload configuration (as further described below).Processing platform 8404 may include one or more processors configuredto perform processing functions (for example, cloud processingfunctions). In some aspects, processing platform 8404 may include one ormore hardware accelerators configured with digital hardware logic toperform dedicated processing tasks (where processing platform 8404 mayhand off these dedicated processing tasks for execution by the hardwareaccelerators). Processing function memory 8406 may be a memoryconfigured to store the software for one or more processing functions,which processing platform 8404 may retrieve and execute with itsprocessing resources. Cloud storage 8408 may be a memory configured tostore various data, which cloud server 8020 may retain for later accessby other devices of local network 8002.

The operation and interaction of these components for dynamic localserver processing offload will now be described. FIG. 85 shows exemplarymessage sequence chart 8500 illustrating the processing and flow ofinformation for dynamic local server processing offload according tosome aspects. As shown in FIG. 85 , the dynamic local server processingoffload may involve cloud server 8020 (or, alternatively, any othercloud server in cloud network 8016), local server 8010, a traffic filter8114/8304 executed at network access node 8006 or UPF server 8012, andterminal devices 8004 a-8004 f.

At stage 8502, cloud server 8020 (e.g., controller 8402) may determinethe processing offload configuration, which may define the amount andtype of local server processing that local server 8010 will perform aspart of the dynamic local server offload processing. The processingoffload configuration can include, for example, an amount of processingfor local server 8010 to perform, the type of target data for localserver 8010 to perform the processing on, and/or a processing function(e.g., the type of analytics) for local server 8010 to perform on thetarget data.

Accordingly, in some aspects controller 8402 of cloud server 8020 maydetermine an amount of processing for local server 8010 to perform instage 8502. There may generally be a tradeoff between the amount oflocal processing done at local server 8010 and the amount of datatransferred and/or stored in cloud server 8020, where more processing ofthe raw data by local server 8010 may result in a smaller amount of datatransferred to cloud server 8020 (as the processed data may be smallerin size than the raw data). Cloud server 8020 may therefore considerthis tradeoff when determining the amount of processing for local server8010 to perform. In some aspects, controller 8402 may execute a decisionalgorithm to determine the amount of processing for local server 8010.For example, controller 8402 may identify the current processing load(e.g., CPU usage) of local server 8010, a current temperature of localserver 8010, and/or a throughput of data that needs to be processed.Controller 8202 of local server 8010 can periodically report thisinformation to controller 8402 of cloud server 8020. In some aspects,controller 8402 may provide these parameters as input parameters to thedecision algorithm, which may use a predefined computation thatcalculates an amount of processing for local server 8010 to performbased on the inputs. In some aspects, the decision algorithm maydetermine whether any of the parameters are above certain thresholds.For example, controller 8402 may determine whether the currentprocessing load of local server 8010 (e.g., of processing platform 8204)is above a load threshold, determine whether the current temperature oflocal server 8010 (e.g., of processing platform 8204) is above atemperature threshold, and/or determine whether the throughput of datais above a throughput threshold. Controller 8402 may then determine theamount of processing based on whether any (or which of) the inputparameters are above their respective thresholds. In some aspects,controller 8402 may also consider its own processing load andtemperature (e.g., of processing platform 8404) when determining theamount of processing, such as by using its own processing load andtemperature as input parameters to the decision algorithm.

In some aspects, controller 8402 of cloud server 8020 may also select aprocessing function for local server 8010 to perform in stage 8502. Forexample, depending on the use case, there may be numerous differentprocessing functions that local server 8010 can perform on the raw data.With reference to the exemplary factory and warehouse use casesintroduced above, the processing function can include various types ofprocessing on sensing and/or operational data to determine a currentscenario of the factory or warehouse, such as evaluating the sensingand/or operational data to determine where certain objects are located,what the current environment is (e.g., temperature), what the progressof certain tasks is, whether and where any errors are occurring, andother types of information about the current scenario in the factory orwarehouse. In some aspects, the processing function selected bycontroller 8402 may be dependent on the amount of processing selectedfor local server 8002 by controller 8402. For example, if the amount ofprocessing selected by controller 8402 is low, the processing functionmay consequently involve a low amount of processing (and vice versa forhigh amounts of processing). Further examples of use cases andprocessing functions are discussed below regarding stage 8518.

In some aspects, controller 8402 of cloud server 8020 may also selectthe type of target data that local server 8010 will perform theprocessing function on. The target data can be a specific subset of theraw data, and can therefore depend on the processing function. Forexample, if the processing function involves processing image, video,and/or positional raw data provided by terminal devices 8004 a-8004 f todetermine where certain objects are located, cloud server 8020 mayselect image, video, and/or positional raw data as the target data. Inanother example, if the processing function involves processingtemperature, humidity and/or pressure raw data provided by terminaldevices 8004 a-8004 f to monitor the environment of the operating area,cloud server 8020 may select temperature, humidity and/or pressure rawdata as the target data. In another example, if the processing functioninvolves processing diagnostic raw data provided by terminal devices8004 a-8004 f (e.g., where terminal devices 8004 a-8004 f areconnectivity-enabled assembly line or factory machines) to monitor forerrors or malfunction, cloud server 8020 may select diagnostic raw dataas the target data. In another example, if the processing functioninvolves processing raw data from specific terminal devices, such asonly from terminal device 8004 a, cloud server 8020 may select raw dataoriginating from terminal device 8004 a as the target data. The type oftarget data involved in the processing function may also impact theamount of processing. For example, various types of target data may havedifferent processing costs, where image, video, and gaming data can havehigh processing cost, audio can have medium processing cost, and datafor statistical analysis can have low processing cost.

In some aspects, cloud server 8020 may select which type of target datato offload to local server 8010 for processing based on underlyingrequirements of the data. For example, in a vehicular use case,latency-sensitive data (e.g., data related to security and safety usecases, such as processing of warning message of vehicles, control oftraffic light, assistance for vehicle overtaking or road cross over) canbe assigned as target data to local server 8010 for local processing. Asit is processed locally within the local network 8002, a round trip tocloud server 8020 for processing can be avoided. Other latency-tolerantdata, such as data related to parking management or image processing forvehicle count, has lower latency requirements and can be offloaded tocloud server 8020. Controller 8402 of cloud server 8020 may use asimilar division of latency-sensitive vs. latency-critical data todecide which raw data to assign as target data for processing at localserver 8010 and which to process at cloud server 8020 for various otherapplicable use cases.

Another example in which latency-sensitive raw data can be processedlocally is a production chain use case, such as a production chain forautomobiles, motors, engines, processors, and other manufactured goodsthat are made with a complex or sensitive procedure. In this use case,terminal devices 8004 a-8004 f may be sensors that continuously monitorthe temperature, humidity, position of pieces, humidity, vibrationlevel, air component readings, position and angle for arms and digits offactory robots performing the assembly, and various other parametersrelevant to the production. These monitored parameters may be sensitive,and the raw data may need to be quickly processed and reacted to, suchas to stop the assembly in case of error and/or to send warning messageto a maintenance team if an abnormal event is observed. Accordingly,controller 8402 of cloud server 8020 may select this data as target datafor offload to local server 8010 for processing. Other raw data such aspiece counts, warehouse stock maintenance, and security video may havemore tolerant latency demands (e.g., may not need a very short reactiontime). Controller 8402 may therefore decide to exclude this data fromthe target data that will be offloaded to local server 8010.

In some aspects, controller 8402 of cloud server 8020 may also determinea filter template based on the target data in stage 8502. The filtertemplate may be a set of parameters that can be used to identify thetarget data when applied to a stream of raw data. Accordingly, when atraffic filter (e.g., traffic filter 8114 of network access node 8010 ortraffic filter 8304 of UPF server 8012) applies the filter template to astream of raw data, the traffic filter may be able to select and extractthe raw data that matches the target data (e.g., that matches the filtertemplate) from the stream of raw data. For example, the parameters ofthe filter template can identify a specific data type, such as image,video, positional, temperature, humidity, pressure, and/or diagnosticdata as introduced in the above examples. In another example, theparameters of the filter template can identify a specific origin and/ordestination of the raw data (for example, based on network addresses inpacket headers, such as based on a 5-tuple). The filter template cantherefore be used by a traffic filter to isolate the target data fromthe other raw data. This is described in detail below for stage 8512.

After determining the processing offload configuration in stage 8502,cloud server 8020 may be configured to send signaling to local network8002 that specifies the processing offload configuration in stages 8504and 8506. In some aspects, controller 8402 of cloud server 8020 may beconfigured to handle communication tasks between network nodes, andaccordingly may be configured to transmit the processing function tolocal network 8002 (e.g., over a logical connection that uses backhaul8014 for transport). For example, as shown in FIG. 85 , cloud server8020 may provide the processing function to local server 8010 in stage8504 (e.g., may send signaling that specifies the processing function).Local server 8020 may then configure itself to perform the processingfunction. For example, in some aspects local server 8010 may bepreconfigured to perform a plurality of preinstalled processingfunctions. Accordingly, the plurality of preinstalled processingfunctions may be loaded into processing function memory 8206 prior toexecution of message sequence chart 8500 (e.g., as part of an offlineconfiguration process, or a periodic update procedure that loads newand/or update preinstalled processing functions into processing functionmemory 8206). Accordingly, in some cases cloud server 8020 may selectthe processing function from the plurality of preinstalled processingfunctions in stage 8502, and may send signaling that includes anidentifier that identifies the processing function to local server 8010in stage 8504. Controller 8202 of local server 8010, which may beconfigured to handle communications with other network nodes, mayreceive the identifier of the processing function and may identify theprocessing function from the plurality of preinstalled processingfunctions. Controller 8202 may then instruct processing platform 8204 toretrieve and load the processing function from processing functionmemory 8206, thus configuring local server 8010 to perform theprocessing function.

In some aspects, cloud server 8020 may send the software for theprocessing function to local server 8010. For example, in some caseslocal server 8010 may not be configured with preinstalled processingfunctions, or cloud server 8020 (e.g., controller 8402) may select aprocessing function that is not one of the preinstalled processingfunctions of local server 8010. Accordingly, in some cases local server8010 may not initially have the software for the processing function.After selecting the processing function in stage 8502, controller 8402of cloud server 8020 may therefore retrieve the software for theprocessing function and send signaling that includes the software forthe processing function to local server 8010. For example, cloud server8020 may store its own plurality of processing functions in processingfunction memory 8406 that cloud server 8020 can retrieve and provide tolocal server 8010. Controller 8202 of local server 8010 may then receivethe software for the processing function, and may provide it directly toprocessing platform 8204 and/or may provide it to processing functionmemory 8206 for storage. In some aspects where the procedure of messagesequence chart 8500 is repeated multiple times, processing functionmemory 8206 of local server 8010 may store the software for the variousprocessing functions provided by cloud server 8020, and accordingly maybe able to locally retrieve the software for the stored processingfunctions (which may thus be considered preinstalled processingfunctions once stored in processing function memory 8206) withoutdownloading it from cloud server 8020.

In some aspects, cloud server 8020 may send an identifier for theprocessing function to local server 8010 in stage 8504. Controller 8202of local server 8010 may then download the software for the processingfunction from another location, such as an external data network.Accordingly, in these various aspects cloud server 8020 may indicate theprocessing function to local server 8010 in stage 8504 and local server8010 may configure itself to perform the processing function.

As previously indicated, local network 8010 may include a trafficfilter, located at network access node 8006 and/or UPF server 8012, thatis configured to apply a filter template for selecting target data fromthe raw data to route to local server 8010. In aspects where the trafficfilter is located at network access node 8006, the traffic filter may betraffic filter 8114 as shown in FIG. 81 . In aspects where the trafficfilter is located at UPF server 8012, the traffic filter may be trafficfilter 8304 as shown in FIG. 83 . Although the traffic filter can belocated at different network locations in different aspects, theoperation of the traffic filter can generally be the same. As shown inFIG. 85 , cloud server 8020 (e.g., controller 8402) may provide thefilter template to traffic filter 8114/8304 in stage 8506. Trafficfilter 8114/8304 may then store the filter template in its templatememory (e.g., template memory 8116 for traffic filter 8114 or templatememory 8306 for traffic filter 8304), where it is available for trafficfilter 8114/8304 to use for subsequent filtering. In some aspects,template memory 8116 or 8306 may store a plurality of preinstalledfilter templates, and cloud server 8020 may send signaling to trafficfilter 8114/8304 that identifies the filter template from the pluralityof preinstalled filter templates.

The filter template may be a set of parameters that identifies aspecific target data from the raw data (e.g., a specific subset of theraw data), and can be used to isolate the target data from the other rawdata. As shown in FIG. 85 , terminal devices 8004 a-8004 f may begenerating raw data in stage 8508, where the raw data can be variousdifferent types of sensing and/or operational data. In some cases, stage8508 may be a continuous procedure, where terminal devices 8004 a-8004 fcontinuously generate raw data. Terminal devices 8004 a-8004 f may thensend the raw data through the local network on the user plane in stage8510, such as by transmitting the raw data to network access node 8006over the radio access network of local network 8002 using theappropriate communication protocols.

As traffic filter 8114/8304 is placed on the user plane in local network8102, traffic filter 8114/8304 may have access to the raw datatransmitted by terminal devices 8004 a-8004 f. In some aspects, terminaldevices 8004 a-8004 f may be configured to transmit the raw data on anend-to-end bearer (e.g., application and/or transport layer) betweenterminal devices 8004 a-8004 f and cloud server 8020. In these aspects,the positioning of traffic filter 8114/8304 on the user plane may enabletraffic filter 8114/8304 to intercept the raw data on the end-to-endbearer. Accordingly, traffic filter 8114/8304 may intercept the raw dataon the end-to-end bearer, and may then apply the filter template to theraw data to identify raw data that matches the filter template in stage8512. For example, where the filter template defines one or moreparameters that identify the target data, traffic filter 8114/8304 mayevaluate the raw data to determine whether properties of the raw datamatch the one or more parameters. In some aspects, traffic filter8114/8304 may utilize packet inspection (e.g., DPI) to evaluate packetsof the raw data to determine whether the packets match the one or moreparameters. In various aspects, the one or more parameters may identifya specific type of raw data (e.g., any one or more of the specificcategories of sensing or operational data), a terminal device or a typeof terminal device from which the raw data originates, a location of theterminal device from which the raw data originates, etc. In someaspects, this information may be included in packet headers, and trafficfilter 8114/8304 may utilize packet inspection to evaluate theinformation in the packet headers. If the information in the packetheaders matches the parameters of the filter template, traffic filter8114/8304 may classify packets as target data.

In some aspects, the filter template can be based on 5-tuples (or someother or similar set of parameters of the same or another size): sourceIP address, destination IP address, source port, destination port, andprotocol type. Accordingly, controller 8402 may define one or more ofthese 5-tuples that identify specific data flows originating from one ormore of terminal devices 8004 a-8004 f, and may indicate theseidentified 5-tuples in the filter template. Traffic filter 8114/8304 maythen be configured to reference the 5-tuples in the filter template(e.g., stored in the template memory) when performing packet inspectionon packets. Traffic filter 8114/8304 may be configured to identifypackets that match one of the 5-tuples and to classify these packets astarget data.

Additionally or alternatively to 5-tuples, the filter template andcorresponding filtering by traffic filter 8114/8304 can be based onbearer ID (e.g., where the data is sent and/or on which flow), qualityflow indicator (e.g., in a Service Data Adaptation Protocol (SDAP)header), protocol header at session layer, a device ID for the devicefrom which the packets originate, a location of the device from whichthe packets originate, a service ID from the session or applicationlayer, and/or packet size.

Traffic filter 8114/8304 may therefore select raw data that matches thefilter template as the target data, and may then route the target datato local server 8010 for local processing. Traffic filter 8114/8304 mayalso route other data of the raw data to cloud server 8020. In somecases, the target data and the other data may be mutually exclusive(e.g., where the other data is all of the raw data except for the targetdata). In other cases, the target data and the other data may overlap,such as where some of the raw data is used for both local processing atlocal server 8010 and for cloud processing at cloud server 8020.

As shown in FIG. 85 , local server 8010 may then receive the target datafrom traffic filter 8114/8304 (e.g., at controller 8202). Local server8010 may then apply the processing function to the target data in stage8518. As previously indicated, local server 8010 may have loaded theprocessing function into processing platform 8204 (either by loading apreinstalled processing function from processing function memory 8206,or by receiving the software for the processing function from cloudserver 8020 or another external location). Controller 8202 of localserver 8010 may therefore route the target data to processing platform8204, which may execute the processing function on the target data toobtain processed data. In some cases, the processing function mayencompass part or all of the processing that would otherwise beperformed on the raw data by a cloud server when using cloud processing.However, as local server 8010 may perform the processing function withinlocal network 8002, this architecture may avoid sending all the raw datato cloud network 8016 over backhaul 8014.

This disclosure recognizes numerous different exemplary processingfunctions that can be performed by processing platform 8204 on thetarget data in stage 8518. These exemplary processing functions candepend on the purpose and/or deployment conditions of local network8002, such as the type of operating area (e.g., a factory or warehouse)that local network 8002 is serving. In some cases, the processingfunction performed by processing platform 8204 can be related toanalytics or big data. Various examples of processing functions caninclude, without limitation:

-   -   Processing raw video, image, or audio data provided by the        terminal devices for monitoring or sensing purposes in the        operating area. This can be used for object recognition (e.g.,        to track objects or identify their positions), surveillance        (e.g., to identify permitted persons/objects vs. intruders),        etc.    -   Processing raw position data (e.g., spatial position or movement        (velocity or acceleration data)) to determine positions of the        terminal devices in the operating area.    -   Processing environmental data, such as temperature, humidity,        wind, and/or pressure, for some operating area with sensitive or        controlled environmental conditions.    -   Factory or warehouse monitoring. For example, tracking the        locations of objects in a warehouse and/or monitoring the        movement of factory robots/workers in the warehouse.        Additionally or alternatively, tracking the movement of parts        and components in a factory, or monitoring the assembly        progress.    -   Shopping mall monitoring. For example, tracking the goods        movement from shelves to payment, detecting when goods or        missing triggering automatically new orders or refill of the        shelves, tracking date, stay duration in the shelves,        controlling payment compared to the number of good leaving the        shelves to detect fraud.    -   Monitoring of transport control data in a train station of        airport, controlling data from sensors and vehicle to coordinate        traffic and detect potential issue. For example, this processing        can assist the supervision and maintenance of the traffic, such        as by checking fuel level, need for restocking, light control,        spare part availability.    -   Hospital monitoring check for equipment status, medicament        storage condition, and restocking needs.    -   Local server in a vehicle processing data from multiple sensors        such as camera or laser equipment in front, rear or side of the        car, motor engine control data, tire pressure, speed, braking        information, route followed by the vehicle and sending to the        cloud only a summary or statistic of the processed data or        sending the data only when matching some reporting criteria such        as threshold or predefined value.    -   Local server in a road side unit, processing data received from        vehicle using for instance V2X signaling or processing data        received from various sensor installed near the street such as        camera or speed control unit or processing data received from        traffic sign or display or from parking area.    -   Processing of event and information to send statistic results to        a cloud (for instance average value, periodicity, . . . ) or to        send data to the cloud when the value of the processed data is        above or below some threshold or is having certain value.    -   Various types of analytics related to any of the above examples.    -   Any combination of these or others.

After applying the processing function on the target data and obtainingthe processed data, local server 8010 may in some cases send theprocessed data to the cloud server in stage 8520. For example,controller 8202 of local server 8010 may send the processed data tocloud server 8020 via UPF server 8012 and/or backhaul 8014. In someaspects, the processing function executed by local server 8010 may onlybe part of the overall scheduled processing for the target data.Accordingly, cloud server 8020 may be configured to perform theremainder of the overall scheduled processing on the processed data toobtain output data. For example, controller 8402 may instruct processingplatform 8404 to load the remaining processing function (constitutingthe remainder of the overall scheduled processing) from processingfunction memory 8406. Alternatively, controller 8402 may be configuredto download the remaining processing function from an external network,such as over the Internet. Once loaded, processing platform 8404 may beconfigured to execute the remaining processing function on the processeddata to obtain the output data. In other aspects, the processingfunction performed by local server 8010 may be the entirety of theoverall scheduled processing for the target data, and the processed datamay thus be the output data.

In some aspects, cloud server 8020 may be configured to provide cloudstorage by storing the output data, such as at cloud storage 8408. Thiscan enable a customer (e.g., a person or computerized entity that usesthe output data) to remotely query the cloud server for the output data.Accordingly, the customer may remotely connect to cloud server andrequest the output data (e.g., all or part of the output data), inresponse to which controller 8402 may retrieve the requested output datafrom cloud storage 8408 and send the requested output data back to thecustomer. This can be applicable, without loss of generality, to caseswhere the data is analytics data, which the customer can use to manage aparticular enterprise located at the operating area (for example, afactory, warehouse, or other type of enterprise).

In some aspects, the processed and/or output data may be used withinlocal network 8002. For example, the processed and/or output data may beused by terminal devices 8004 a-8004 f, and/or by otherconnectivity-enabled devices operating on local network 8002. Forinstance, terminal devices 8004 a-8004 f can refine their sensing and/oroperational behavior based on the processed and/or output data. Inanother example, other connectivity-enabled devices in local network8002, such as warehouse robots or smart assembly line devices, may usethe processed and/or output data to improve their operation and/or adaptto changes in the operating area.

In cases where the processed data (e.g., the data obtained by localserver 8010) is used in local network 8002, local server 8010 may beconfigured to provide the processed data back to local network 8002directly (e.g., without sending the processed data outside of localnetwork 8002). For example, local server 8010 (e.g., controller 8202)may be configured to transmit the processed data to network access node8006, which may then wirelessly transmit the processed data to theappropriate devices of local network 8002. As the processed data may notleave local network 8002, this can avoid the latency involved in around-trip transfer to and from cloud server 8020 for cloud processing.This can, without limitation, be useful in cases where the raw dataand/or processed data is time-sensitive, such as when the raw data isused to monitor for errors and emergencies, or to avoid collisions.

For example, when using raw data to monitor the conditions of anenvironment-sensitive environment, or to track factory parts or workerrobots, it can be beneficial to respond quickly to the raw data.Accordingly, traffic filter 8114/8304 can identify the target data inthe raw data that is used for this processing, and then route the targetdata to local server 8010. Local server 8010 can then apply theprocessing function to obtain the processed data, and then feed theprocessed data directly back into local network 8002. For example, ifthe processing function involves processing raw temperature and/orhumidity data do determine whether the environment of the operating areais inside a controlled range. If the processing function determines thatthe temperature or humidity is outside of the controlled range, localserver 8010 can provide instructions (e.g., wirelessly via networkaccess node 8006) to appropriate devices in local network 8002 that canmanage the environment (e.g., humidifiers/de-humidifiers, heaters,and/or coolers), which can then operate to bring the environment backwithin the controlled range. In another example, if a factory orwarehouse product moves into the wrong location, or is a factory robotis on a collision course, the processing function may detect the error.Local server 8010 may then provide instructions (e.g., via wirelesslyvia network access node 8006) to appropriate devices in local network8002 that can remedy or avoid the error, such as by instructing afactory robot or smart assembly line device to move the product to thecorrect location or by instructing the factory robot to correct itscourse.

In cases where the output data is used by local network 8002, cloudserver 8020 may be configured to transmit the output data back to localnetwork 8002 over backhaul 8014. In some cases, cloud server 8020 (e.g.,controller 8402) may be configured to transmit the output data directlyto the appropriate devices in local network 8002 that use the outputdata, such as over an end-to-end bearer with the appropriate devices. Insome cases, cloud server 8020 may be configured to send the output datato network access node 8006, which may then be configured to determinethe appropriate devices to which the output data should be sent.

In some cases, cloud server 8020 may be configured to send the outputdata to local server 8010, where controller 8202 may be configured toevaluate the output data and determine where the output data should besent. For example, controller 8202 may identify the appropriate devicesof local network 8002 to which the output data should be sent, and maythen send the output data to the identified appropriate devices. In someaspects, controller 8202 may determine the output data is scheduled forfurther processing, and may provide the output data to processingplatform 8204. Processing platform 8204 may then execute anotherprocessing function on the output data (e.g., different from theprocessing function of stage 8518), and may provide the resulting datato controller 8202. Controller 8202 may then identify the appropriatedevices and transmit the resulting data to the appropriate devices.

In some aspects, the processing offload configuration for the dynamiclocal server processing offload can be dynamic. For example, as shown inFIG. 85 , controller 8402 of cloud server 8020 may be configured todetermine an updated processing offload configuration in stage 8522. Forinstance, controller 8402 may determine that the amount and/or type ofprocessing performed by local server 8010 should be updated (as furtherdescribed below). Accordingly, controller 8402 may select an updatedprocessing function and/or determine an updated filter template 8526 forthe updated processing offload configuration in stage 8522. A shown inFIG. 85 , controller 8402 may then send the updated processing function(e.g., the software or an identifier) to local server 8010 in stage8524, and may send the updated filter template to traffic filter8114/8304 in stage 8526. Terminal devices 8004 a-8004 f, local server8010, and traffic filter 8114/8304 may then repeat the procedure ofstages 8508-8520 with the updated processing function and updated filtertemplate. The amount of processing, type of processing, and/or type oftarget data can therefore change over time.

In some aspects, cloud server 8020 may be configured to trigger theseupdates to the processing offload configuration based on dynamicparameters. As previously described, in some aspects cloud server 8020may be configured to determine an amount of processing for local server8010 to perform based on one or more input parameters, includingprocessing load of local server 8010, temperature of local server 8010,and the throughput of data. In some aspects, controller 8402 of cloudserver 8020 may be configured to track these input parameters over time,and to adapt the amount of processing for local server 8010 according tochanges in these input parameters. In some aspects, cloud server 8020may monitor these input parameters and input them into the decisionalgorithm, which may then output an updated amount of processing forlocal server 8010 to perform. Controller 8402 of cloud server 8020 maythen update the processing function and filter template to reflect thechange in the amount of processing for local server 8010, and may obtainan updated processing function and updated filter template.

In other aspects, controller 8402 may monitor the input parameters andcompare the input parameters to thresholds to determine whether toupdate the processing offload configuration. For example, controller8402 may compare the current processing load of local server 8010,current temperature of local server 8010, current processing load ofcloud server 8020, current temperature of cloud server 8020, and/orthroughput of data to corresponding thresholds, and may decide whetherto update the processing offload configuration based on whether any ofthe input parameters are above their corresponding thresholds. Forinstance, if the current processing load or current temperature of localserver 8010 is above its corresponding threshold, controller 8402 maydecide to reduce the amount of processing assigned to local server 8010.In another example, if the current processing load or currenttemperature of cloud server 8020 is above its corresponding threshold,controller 8402 may decide to increase the amount of processing assignedto local server 8010 (which can reduce the processing burden on cloudserver 8020). Controller 8402 may be configured to determine an updatedprocessing function and updated filter template based on such decisionsto increase or decrease the amount of processing assigned to localserver 8010.

In some cases, controller 8402 of cloud server 8020 can base thesedeterminations on the occurrence of peak times that involve a largeramount of processing. In one example, local server 8010 may be used toprocess data of many sensors, such as cameras, that are monitoring anoperating area. During nighttime, there may be less people in theoperating area, and special nighttime sensors (such as night-vision orthermal cameras) may be switched on to enable low-light surveillance.The processing involved for monitoring these special nighttime sensorsmay be more demanding than for daytime sensors, and nighttime maytherefore be a peak time. In another example, local server 8010 may beused to process sensing data related to a commercial center or warehouseto which delivery vehicles arrive to deliver goods. If the deliveryvehicles arrive at a certain time of day, such as in the morning, theremay be corresponding peak times when there is more data to be processed.In another example, local server 8010 may be part of a roadside unit(RSU). If the RSU is playing the role of a gateway and uses sensing datafrom multiple sensors (such as cameras and radar sensors) to control adigital sign or other traffic signal, the RSU may have greaterprocessing demands during rush hour when there are more vehicles on theroad (e.g., morning hours before work, and evening hours right afterwork). There may therefore be peak times during rush hour. During thesepeak times, as well as other peak times unique to various otherapplicable use cases, controller 8402 may adapt the processing offloadconfiguration to shift processing to cloud server 8020. Controller 8402may therefore determine updated processing functions and filtertemplates that involve more processing at cloud server 8020.

In some aspects, controller 8402 may additionally or alternatively beconfigured to adapt the processing offload configuration based on thecurrent demands of local network 8002. For example, in some cases localnetwork 8002 can have varying latency demands, where during some periodslocal network 8002 has strict latency demands for receiving processedand/or output data while in other periods local network 8002 hastolerant latency demands. Accordingly, during periods where localnetwork 8002 has strict latency demands, controller 8402 of cloud server8020 may be configured to shift the processing offload towards localnetwork 8002 (e.g., may select a processing function that involves moreprocessing at local server 8010). This may enable local server 8010 toperform more processing and consequently quickly feed processed databack into local network 8002 as needed. Conversely, during periods wherelocal network 8002 has tolerant latency demands, controller 8402 may beable to shift the processing offload back to cloud server 8020.

Controller 8402 may be configured to consider various additional oralternative dynamic parameters when deciding whether to adapt theprocessing offload configuration. For example, controller 8402 mayconsider the cost to transmit the data from local network 8002 to cloudserver 8020, the amount of raw data local network 8002 is transmittingto cloud server 8020, the power consumption of local server 8010 (e.g.,by shifting processing offload to cloud server 8020 when the powerresources of local server 8010 are low). These criteria may vary overtime, and controller 8402 may consequently monitor them over time (e.g.,by monitoring its own status and/or by receiving reports from localserver 8010) and determine appropriate adaptations to the processingoffload configuration as needed.

In an example regarding cost as a dynamic parameter, a company may pay anetwork provider based on the amount of data transferred (e.g., overbackhaul 8014). The cost may optionally depend on the network load, datatransfer may have a higher cost when network load is high (e.g., ofbackhaul 8014) and lower cost when network load is low. The cost of datatransfer can also vary based on other factors. Controller 8402 maytherefore adapt the amount of processing done at local server 8010 basedon the cost of data transfer at a given time, where controller 8402 mayshift more processing (by determining a corresponding updated processingfunction and updated filter template) to local server 8010 when cost ishigh and shift more processing to cloud server 8020 when cost is low.

In an example using power consumption as a dynamic parameter, powerconsumption may play a role when local network 8002 is operating on adefinite power source, such as a battery. This can occur, for example,when an indefinite power source is temporarily unavailable, such as forad hoc camp establishment (e.g., for safety, area exploration, temporaryinstallation). In such cases, controller 8402 may evaluate and comparethe relative amount of energy consumption of local vs. cloud processing.For example, controller 8402 may estimate the amount of energyconsumption for local server 8010 to perform the processing function onthe raw data and to transmit the target data (assumed to be smaller insize), and also estimate the amount of energy consumption for localnetwork 8002 to transmit the larger amount of raw data (e.g., withoutlocal processing). Controller 8402 may use historical data of energyconsumption reported by local network 8002 to perform these estimations,and may consider the amount of data being generated by local network8002 to compute the estimates using the historical data as a model ofthe energy consumption. Controller 8402 may then adapt the amount ofprocessing assigned to local server 8010 to minimize energy consumption(e.g., using a gradient descent algorithm that attempts to find theminimum energy consumption with the amount of processing done locallyvs. at the cloud being the variables. This analysis can also depend onthe type of processing function, such as whether the processing functionis for audio, video, or data statistics. The analysis can also depend onthe radio access technology used for data transfer, such as LTE, 2G,WLAN, BT, LORA, Sigfox, or another type of radio access technology.

In the exemplary setting of FIG. 85 described above, cloud server 8020may be configured to determine the processing offload configuration forthe dynamic local server processing offload. In other aspects, localserver 8010 may be configured to determine the processing offloadconfiguration, and controller 8202 may of local server 8010 maytherefore be configured to perform any decision-making described abovefor controller 8402 (e.g., for stages 8502 and 8518). FIG. 86 showsexemplary message sequence chart 8600, which depicts some aspects wherelocal server 8010 is configured to determine the processing offloadconfiguration. As shown in FIG. 86 , controller 8202 of local server8010 may be configured to determine the processing offload configurationin stage 8602. This can include selecting a processing function forlocal server 8010 to execute and/or determining a filter template. Insome cases, local server 8010 may already have the processing functionstored on processing function memory 8206 as a preinstalled processingfunction, and controller 8202 may instruct processing platform 8204 toload the software for the processing function from processing functionmemory 8206. In other cases, such as that shown in FIG. 86 , localserver 8010 may not already have the processing function stored atprocessing function memory 8206. Controller 8202 may therefore downloadthe software for the processing function in stage 8604, such as fromcloud server 8020 (which may, for example, have the software for theprocessing function stored at its processing function memory 8206) orfrom an external network (e.g., over the Internet). This can includereceiving signaling that includes the software for the processingfunction. Controller 8202 may then provide the software for theprocessing function to processing function memory 8206 for storage andlater retrieval, or may provide the software for the processing functiondirectly to processing platform 8204.

Controller 8202 may therefore configure local server 8010 to perform theprocessing function, such as by loading the software for the processingfunction into processing platform 8204. Controller 8202 may also sendsignaling to traffic filter 8114/8304 in stage 8606 that specifies thefilter template (e.g., signaling that includes the filter template, orsignaling that identifies the filter template from a plurality ofpreinstalled filter templates). Terminal devices 8004 a-8004 f, trafficfilter 8114/8304, local server 8010, and cloud server 8020 may thenperform stages 8608-8622 in the manner described above for stages8508-8522 in FIG. 85 . Similar to the case of controller 8402 of cloudserver 8020 in FIG. 85 , controller 8202 of local server 8010 may beconfigured to determine an updated processing offload configuration instage 8622. For example, controller 8202 may monitor one or more dynamicparameters and adapt the processing offload configuration, and mayselect an updated processing function and an updated filter template.Controller 8202 may execute this functionality in any manner describedabove for controller 8402. Controller 8202 may then download the updateddata processing function in stage 8624, if needed, and send the updatedfilter template to traffic filter 8114/8304 in stage 8626.

As shown in the exemplary setting of FIG. 80 , in some cases localnetwork 8002 may optionally also include CPF server 8008. In someaspects, CPF server 8008 may be responsible for propagating theprocessing offload configuration, as selected by cloud server 8020,within local network 8002. For example, controller 8402 of cloud server8020 may maintain a control signaling interface with CPF server 8008through which controller 8402 may exert control over the dynamic localserving processing offload in local network 8002. For instance, insteadof having a signaling interface with local server 8010 and/or trafficfilter 8114/8304 (for example, that could be used to send processingfunctions and/or filter templates), controller 8402 may use the controlsignaling interface with CPF server 8008 to send the processing offloadconfiguration (e.g., including the processing functions and/or filtertemplates for the selected processing offload configuration) to CPFserver 8008. CPF server 8008 may then be configured to provide theprocessing function to local server 8010 (e.g., via a signalinginterface between CPF server 8008 and controller 8202 of local server8010) and/or to provide the filter template to traffic filter 8114/8304(e.g., via a signaling interface between CPF server 8008 and networkaccess node 8006 and UPF server 8012). Local server 8010 and trafficfilter 8114/8304 may then apply the processing function and/or filtertemplate in the manner described above.

Some of the aspects described above use an architecture where thetraffic filter sits on the user plane in either network access node 8006or UPF server 8012, which can enable the traffic filter to tap raw dataon the user plane and re-route target data to local server 8020.Additionally or alternatively, the traffic filter may be implementedlocally at terminal devices 8004 a-8004 f. Accordingly, the trafficfilter may evaluate the raw data before it is sent from terminal devices8004 a-8004 f to identify the target data (e.g., raw data that matchesthe one or more parameters that define the filter template). The trafficfilter can then send the target data to local server 8010 (for example,over a special bearer that the traffic filter establishes withcontroller 8202 of local server 8010).

FIG. 87 shows an exemplary internal configuration of terminal devices8004 a-8004 f according to some aspects. As shown in FIG. 87 , terminaldevices 8004 a-8004 f may include antenna system 8702, RF transceiver8704, and baseband modem 8706 (including digital signal processor 8708and protocol controller 8710), which may be respectively configured inthe manner of antenna system 202, RF transceiver 204, and baseband modem206 of terminal device 102 shown in FIG. 2 .

Terminal devices 8004 a-8004 f may further include application platform8712. As shown in FIG. 87 , application platform 8712 may includetraffic filter 8714, template memory 8716, and raw data generator 8718.Similar to that described above for traffic filters 8114 and 8304,traffic filter 8714 may be a filter (e.g., a software filter) configuredto evaluate raw data to identify target data (from the raw data) thatmatches one or more parameters of a filter template. For example,traffic filter 8714 may be configured to perform packet inspection(e.g., DPI) on a stream of packets containing raw data, and to identifyone or more characteristics of each data packet (e.g., based on headerinformation). Traffic filter 8714 may then be configured to determinewhether any of the one or more characteristics of each data packet matchone or more parameters of the filter template. If so, traffic filter8714 may classify the packet as target data, and route the target datato local server 8010. If not, traffic filter 8714 may classify thepacket as other data, and may route the other data along its originallyscheduled path (e.g., on an end-to-end bearer to cloud server 8020).Template memory 8716 may be configured to store the filter template.

Raw data generator 8718 may include one or more components configured togenerate the raw data. The components that make up raw data generator8718 may vary depending on the particular use case of the raw data. Forexample, raw data generator 8718 can include any one or more of: imageor video cameras, microphones, gyroscopes/accelerometers/speedometers,signal-based geopositional sensors (e.g., using Global NavigationSatellite System (GNSS)), thermometers, humidity sensors, wind sensors,barometers, laser or radar sensors, automotive sensors (e.g., formonitoring tire pressure, engine conditions, brakes, route, etc.), orwireless communication circuitry that receives signals from otherdevices (for example, where raw data generator 8718 receives sensing ormonitoring data from other devices that raw data generator 8718subsequently uses as raw data). In some aspects where the raw data isrelated to communications by baseband modem 8706, such as where the rawdata relates to radio conditions experienced by baseband modem 8706, rawdata generator 8718 may interface with baseband modem 8706. Basebandmodem 8706 may then provide the raw data to raw data generator 8718 overthe interface.

Traffic filter 8714 may be configured to operate a similar or samemanner as traffic filters 8114 and 8304 as previously described. Forexample, local server 8010 (e.g., controller 8202) or cloud server 8020(e.g., controller 8402, which can be directly or via CPF server 8008)may send the filter template to traffic filter 8714. The filter templatemay be sent wirelessly, where the local server 8010 or cloud server 8020sends the filter template to network access node 8006, and networkaccess node 8006 wirelessly transmits the filter template as basebanddata to baseband modem 8706. Baseband modem 8706 may then receive andprocess the baseband data to obtain the filter template, and may providethe filter template to template memory 8716.

Traffic filter 8714 may then be configured to access template memory8716 and configure itself according to the filter template. Trafficfilter 8714 may then monitor the raw data produced by raw data generator8718 and evaluate the raw data according to the filter template. Trafficfilter 8714 may then identify the target data as the raw data thatmatches the filter template, and the other data as raw data that doesnot match the filter template. Traffic filter 8714 may then send thetarget data on a special bearer between traffic filter 8714 and localserver 8010 (e.g., controller 8202), and may send the other data on, forexample, an end-to-end bearer with cloud server 8020 (e.g., controller8402). The special bearer and the end-to-end bearer may use wirelesstransmission for lower layer transport, and accordingly traffic filter8714 may provide the target data and raw data to baseband modem 8706 forwireless transmission to network access node 8006.

In an exemplary use case focused on wireless communications, localserver 8010 may be configured to assist network access node 8006 withmanaging its radio access network. For example, local server 8010 may beconfigured to perform analytics to optimize its scheduling and resourceallocations. In this example, network access node 8006 may be configuredto use deterministic scheduling to manage radio access by terminaldevices 8004 a-8004 f. Accordingly, network access node 8006 may sendout resource allocations to terminal devices 8004 a-8004 (e.g., to thoseof terminal devices 8004 a-8004 f that in a radio connected state)during each scheduling interval. Terminal devices 8004 a-8004 f may thentransmit and receive on the available radio resources according to theresources allocated to each in their respective resource allocations.

In some cases, the transmission or reception activity by terminaldevices 8004 a-8004 f may follow a pattern over time. For example, someIoT devices may be configured to perform radio activity in adeterministic manner, such as a sensor or image camera that isconfigured to wirelessly report a reading or image every X ms, or avideo camera that wirelessly provides a continuous stream of video data.In these and other similar cases, there may be some underlyingdeterministic pattern in the radio activity by terminal devices 8004a-8004 f. Accordingly, instead of providing resource allocations inresponse to scheduling requests and buffer status reports, it can bebeneficial for network access node 8006 to provide resource allocationsthat follow the deterministic patterns of the radio activity by terminaldevices 8004 a-8004 f. In some aspects, local server 8010 may thereforebe configured to perform a processing function on operational data(e.g., raw data) of network access node 8006 and/or terminal devices8004 a-8004 f to identify deterministic patterns in the radio activityof terminal devices 8004 a-8004 f. Local server 8010 may then provideinstructions (e.g., in the form of processed data) to network accessnode 8006 that informs network access node 8006 how to improve itsscheduling and resource allocations. As network access node 8006 cantherefore tailor its scheduling and resource allocations to thedeterministic patterns of radio activity exhibited by terminal devices8004 a-8004 f, this can improve performance and resource usageefficiency.

In some aspects, this wireless communication-focused use case of dynamiclocal server processing offload may be handled in cooperation by localserver 8010 and cloud server 8020 (e.g., using processing by both localserver 8010 and cloud server 8020), while in other aspects this use casecan be handled within local network 8002 (e.g., independent of cloudservers and using processing by local server 8010). FIG. 88 showsexemplary message sequence chart 8800 describing some aspects where thewireless communication-focused use case is handled in cooperation bylocal server 8010 and cloud server 8020. As shown in FIG. 88 , cloudserver 8020 (e.g., controller 8402) may first determine the processingoffload configuration in stage 8802, and may then send signaling tolocal server 8010 that specifies the processing function in stage 8804and send signaling to traffic filter 8114/8304 in stage 8806 thatspecifies the filter template. In this use case, the processing functioncan be related to pattern recognition analytics, and can process rawdata to identify patterns in radio resource usage. Although notexplicitly shown in FIG. 88 , in some aspects local server 8010 (e.g.,controller 8202) may alternatively be configured to determine theprocessing offload configuration in stage 8802. Traffic filter 8114/8304may be located in either network access node 8006 or UPF server 8012. Insome cases it may be advantageous for traffic filter 8114/8304 to belocated in network access node 8006 due to the increased involvement ofnetwork access node 8006 in this use case.

As shown in FIG. 88 , terminal devices 8004 a-8004 f may perform radioactivity on the radio access network provided by network access node8006 in stage 8808. This can include downlink transmissions, such aswhere network access node 8006 schedules downlink transmissions toterminal devices 8004 a-8004 f by transmitting resource allocations toterminal devices 8004 a-8004 f identifying the radio resources (time andfrequency) for the downlink transmissions and then transmits thedownlink transmission according to the resource allocations. This canalso include uplink transmissions, where terminal devices 8004 a-8004 frequest uplink resources from network access node 8006 (e.g., withscheduling requests and/or buffer status reports) and then receiveresource allocations from network access node 8006 that identify theradio resources that terminal devices 8004 a-8004 f can use to transmitthe uplink transmissions.

As it is related to current communication status and/or previouscommunication history, this information related to the downlink anduplink scheduling may be considered operational data. Terminal devices8004 a-8004 f and network access node 8006 may therefore generate andretain this raw data. For example, in aspects where terminal devices8004 a-8004 f are configured in the manner shown in FIG. 2 , a basebandmodem 206 (e.g., a protocol stack running on protocol controller 210) ofterminal devices 8004 a-8004 f may generate scheduling requests and/orbuffer status reports (for uplink transmissions) and may receiveresource allocations (for uplink and downlink transmissions). In someaspects, baseband modem 206 may then wirelessly transmit this raw datato traffic filter 8114/8304 in stage 8810.

Similarly, in aspects where network access node 8006 is configured inthe manner shown in FIG. 3 , a baseband subsystem 306 (e.g., a protocolstack running on protocol controller 310) may generate resourceallocations (for uplink and downlink transmissions) and may receivescheduling requests and/or buffer status reports. Accordingly, basebandsubsystem 306 may send this raw data to traffic filter 8114/8304 instage 8812. Although FIG. 88 shows a case in which both terminal devices8004 a-8004 f and network access node 8006 provide raw data to trafficfilter 8114/8304, in other aspects only one of terminal devices 8004a-8004 f and network access node 8006 may provide the raw data totraffic filter 8114/8304.

Traffic filter 8114/8304 may then apply the filter template to the rawdata in stage 8814 to identify target data. The target data may be theraw data that is relevant to the pattern recognition analytics of theprocessing function. For example, not all of the raw data provided byterminal devices 8004 a-8004 f and network access node 8006 may relateto the pattern recognition analytics. In one example, the processingfunction may be configured to recognize only one of downlink radioresource usage patterns but not uplink radio resource usage patterns (orvice versa). Accordingly, the filter template may specify that only rawdata relating to downlink transmissions is matching. Traffic filter8114/8304 may therefore identify raw data relating to downlinktransmissions as target data, while identifying the remaining data asother data.

After identifying the target data, traffic filter 8114/8304 may send thetarget data to local server 8010 in stage 8816. As the other data maynot have further relevance (as it may relate to uplink or downlinktransmissions that have already occurred), traffic filter 8114/8304 maydiscard the other data. Local server 8010 (e.g., controller 8202) maythen apply the processing function to the target data in stage 8818. Forexample, this can include applying pattern recognition analytics to thetarget data to identify a deterministic pattern in the radio resourceusage by terminal devices 8004 a-8004 b, such as to identify a regularperiodicity at which one or more (or each of) terminal devices 8004a-8004 b is transmitting or receiving.

As the use case shown in FIG. 88 involves a setting where cloud server8020 also participates in the processing, local server 8010 may send theresulting processed data to cloud server 8020 in stage 8820. In someaspects, the processed data may be usable by network access node 8006without further cloud processing, and local server 8020 may also sendthe processed data to network access node 8006.

Cloud server 8020 may then perform the cloud processing on the processeddata in stage 8824 to obtain output data. For example, the processingfunction performed by local server 8010 in stage 8818 may only be partof the pattern recognition analytics, and cloud server 8020 maytherefore perform the remaining part of the pattern recognitionanalytics in stage 8824. Cloud server 8020 may then provide the outputdata to network access node 8006 in stage 8826.

Network access node 8006 may therefore receive the output data(optionally in addition to the processed data, if applicable), and maythen manage resource allocations in stage 8828 based on the outputand/or processed data. For example, the pattern recognition analyticsmay yield processed and/or output data that identifies a particulardeterministic pattern of radio resource usage. In one example ofidentifying a deterministic pattern, the processed and/or output datamay identify a regular periodicity at which one of terminal devices 8004a-8004 f perform uplink or downlink communications. Network access node8006 (e.g., a scheduler entity of the protocol stack running at protocolcontroller 310) may therefore schedule uplink and or downlink resourceallocations in advance according to the regular periodicity. Forexample, if processed and/or output data identifies that terminal device8004 a performs an uplink transmission (or receives a downlinktransmission) every X ms, network access node 8006 may allocateresources to terminal device 8004 a every X ms (e.g., may allocate radioresources with the regular periodicity).

In another example of identifying a deterministic pattern, such as oneusing a factory or warehouse setting, terminal devices 8004 a-8004 f maybe sensors that send sensing data in a periodic manner and/or with aconstant size. For example, terminal devices 8004 a-8004 f may betemperature sensors, and may perform a temperature measurement every 30s (e.g., with its raw data generator 8718 configured as a thermometer).Terminal devices 8004 a-8004 f send a corresponding packet of raw dataevery 30 s that contains its device/sensor identify, a timestamp, andthe temperature measurement. As terminal devices 8004 a-8004 f may beconfigured similarly, they may therefore send raw data with the same orsimilar packet size and periodicity (e.g., following a same or similardeterministic pattern). Local server 8010 may be configured to identifythis regular periodicity and packet size, such as by either performingpattern recognition analytics on the data sent by terminal devices 8004a-8004 f and/or with predefined knowledge about the sensor configurationof terminal devices 8004 a-8004 f (e.g., that indicates how oftenterminal devices 8004 a-8004 f will be reporting and/or the packetsize). Network access node 8006 may therefore be able to reserveperiodic resources and automatically allocate transmission grants forterminal devices 8004 a-8004 f. Terminal devices 8004 a-8004 f maytherefore not need to request for resources, which can reduce controlsignaling overhead and yield higher radio resource efficiency. Thisconcept of terminal devices with fixed radio activity periodicity and/orpacket size can be expanded to any use case.

Additionally, local server 8010 may be configured to determine whetherterminal devices 8004 a-8004 f are at a fixed location, (e.g., byevaluating position reports provided by terminal devices 8004 a-8004 fto determine their positions over time, such as GNSS position reports).If so, local server 8010 may instruct network access node 8006 (bysending it the processed data) to disable mobility management for thoseof terminal devices 8004 a-8004 f that are at a fixed location. In someaspects, local server 8010 may also instruct network access node 8006 tosimplify the power control algorithm for those of terminal devices 8004a-8004 f that are at a fixed location, as the uplink transmission powerassigned to non-moving terminal devices can be held constant (assumingno change in environment).

FIG. 89 shows exemplary message sequence chart 8900 according to someaspects where the dynamic local server processing offload is handledwithin local network 8002 (e.g., independent of cloud processing). Asshown in FIG. 89 , local server 8010 may first determine the processingoffload configuration in stage 8902. Local server 8010 may thenconfigure itself to perform the processing function (e.g., for patternrecognition analytics), which can include loading software for theprocessing function into processing platform 8204 from processingfunction memory or downloading the software for the processing functioninto processing platform 8204 from an external network. Local server8010 may also send signaling to traffic filter 8114/8304 in stage 8904that specifies the filter template.

Terminal devices 8004 a-8004 f and network access node 8006 may performradio activity in stage 8906, and may send the raw data to trafficfilter 8114/8304 in stages 8908 and 8912. Traffic filter 8114/8304 maythen apply the filter template to the raw data to identify the targetdata in stage 8912, and may send the target data to local server 8010 instage 8914.

Local server 8010 may then apply the processing function to the targetdata in stage 8916, and may obtain processed data. As previouslyindicated, the processing function may relate to pattern recognitionanalytics, and the processed data may indicate deterministic patterns ofradio resource usage by one or more (or each) of terminal devices 8004a-8004 f. Local server 8010 may then send the processed data to networkaccess node 8006 in stage 8918. Network access node 8006 may then usethe processed data in stage 8920 to manage resource allocations forterminal devices 8004 a-8004 f, such as by allocating resourcesaccording to a regular periodicity indicated in the processed data.

In the aspects described above for FIGS. 88 and 89 , the target data mayinclude operational data that is relevant to uplink and downlink radioresource usage by terminal devices 8004 a-8004 f, where the processingfunction may be configured to identify deterministic patterns in radioresource usage. In other aspects, terminal devices 8004 a-8004 f and/ornetwork access node 8006 may provide target data to local server 8010(e.g., via a traffic filter) that local server 8010 can use to identifythe position and/or radio conditions of terminal devices 8004 a-8004 f.For example, local server 8010 may receive target data that includesmeasurement reports and/or position reports for terminal devices 8004a-8004 f. Local server 8010 may then be configured to apply a processingfunction to this target data that is configured to optimize the radiocoverage provided by network access node 8006 to terminal devices 8004a-8004 f.

Accordingly, with reference to FIGS. 88 and 89 , cloud server 8020 orlocal server 8010 may select the processing offload configuration,including the processing function and the filter template, and configurelocal server 8010 to perform the processing function and traffic filter8114/8304 to perform filtering with the filter template. Terminaldevices 8004 a-8004 f and network access node 8006 may then performradio activity and report raw data to traffic filter 8114/8304. The rawdata can include measurement reports by terminal devices 8004 a-8004 fand network access node 8006, such as signal strength measurements,signal quality measurements, channel estimates, measured throughput,measured latency, and/or measured error rate. The raw data can alsoinclude communication reports that detail parameters related to theconfigured transmit power and/or configured modulation and codingscheme. The raw data can also include position reports for terminaldevices 8004 a-8004 f.

Traffic filter 8114/8304 may receive this raw data, and may apply thefilter template to the raw data to identify the target data. In someaspects, the filter template may specify particular terminal devices,and traffic filter 8114/8304 may therefore identify raw data originatingfrom these terminal devices as target data. In other aspects, such aswhere the processing function applies to specific types of the raw data(e.g., to specific measurements), the filter template may identify thesespecific types of raw data. Traffic filter 8114/8304 may thereforeidentify raw data of these specific types as the target data.

Traffic filter 8114/8304 may then provide the target data to localserver 8010. Local server 8010 may then apply the processing function tothe target data to obtain the processed data. In use cases where thedynamic local server processing offload is handled internally withinlocal network 8002, local server 8010 may then provide the processeddata back to network access node 8006. In use cases where the dynamiclocal server processing offload also uses cloud processing, local server8010 may provide the processed data to cloud server 8020. Cloud server8020 may then perform cloud processing on the processed data to obtainoutput data, which cloud server 8020 may then send back to networkaccess node 8006.

Network access node 8006 may then use the processed and/or output datato manage its radio coverage. For example, the various raw data providedby terminal devices 8004 a-8004 f may relate to the radio conditions atvarious different positions around network access node 8006. Theprocessing function may therefore be configured to evaluate thisposition-dependent radio coverage, and to attempt to identifyadaptations that could improve the position-dependent radio coverage. Inone example, the processing function may relate to radio environmentmaps (REMs), which map out radio conditions on a geographic map. Theprocessing function may therefore be configured to generate an REM basedon the raw data, such as by mapping out measurements by position and/orinterpolating between the measurements at different positions to smooththe REM. The processing function may also be configured to generateprocessed or output data that uses the REM to identify adaptationsto-improve the position-dependent radio coverage. For example, given anREM, the processing function may be configured to decide on a particularbeamforming pattern, downlink transmit powers, uplink and downlinktransmit powers, modulation and coding schemes, to enable or disablemeasurement report and cell reselection capability from a terminaldevice, precoding matrices, or any other parameter that network accessnode 8006 can use to impact radio coverage. Accordingly, the processedor output data may specify any of these parameters to network accessnode 8006. Network access node 8006 may then use the parametersspecified in the output data to adjust its radio activity (optionallyalso the radio activity of terminal devices 8004 a-8004 f, such as byassigning a new parameter for terminal devices 8004 a-8004 f to use). Insome cases, this can help to improve radio coverage provided by networkaccess node 8006 to terminal devices 8004 a-8004 f. This can also beperformed in a continuous process, where terminal devices 8004 a-8004 fand network access node 8006 continuously provide raw data to localserver 8010 and/or cloud server 8020, and local server 8010 and/or cloudserver 8020 provide processed and/or output data back to network accessnode 8006 that specifies parameters for improving radio coverage basedon the recent raw data.

In various other aspects, message sequence charts 8800 and 8900 may alsoupdate the processing offload configuration over time (e.g., by cloudserver 8020 and/or local server 8010). In some aspects, message sequencecharts 8800 and 8900 may not include a traffic filter, and terminaldevices 8004 a-8004 f and/or network access node 8006 may transmit theirraw data directly to local server 8010. In other aspects, terminaldevices 8004 a-8004 f and/or network access node 8006 may include thetraffic filter. The traffic filter may evaluate the raw data generatedby baseband modem 206 and baseband subsystem 306, respectively, andidentify the target data from the raw data. The traffic filter may thensend the target data to local server 8010.

FIG. 90 shows exemplary method 9000 of performing processing at a localserver according to some aspects. As shown in FIG. 90 , method 9000includes receiving signaling from a cloud server that specifies aprocessing function assigned for processing offload by the local server(9002), receiving, from a traffic filter, target data that originatesfrom a local network (9004), applying the processing function to thetarget data to obtain processed data (9006), and sending the processeddata to the cloud server for cloud processing (9008).

FIG. 91 shows exemplary method 9100 for performing processing functionsat a local server according to some aspects. As shown in FIG. 91 ,method 9100 includes selecting a processing function for processingoffload (9102), receiving, from a traffic filter, target data thatoriginates from a local network (9104), applying the processing functionto the target data to obtain processed data (9106), and sending theprocessed data to the cloud server for cloud processing (9108).

FIG. 92 shows exemplary method 9200 for performing processing functionsat a local server according to some aspects. As shown in FIG. 92 ,method 9200 includes receiving signaling from a cloud server thatspecifies a processing function assigned for processing offload by thelocal server (9202), receiving, from a traffic filter, target data thatoriginates from a local network (9204), applying the processing functionto the target data to obtain processed data (9206), and sending theprocessed data to the local network (9208).

FIG. 93 shows exemplary method 9300 for performing processing functionsat a local server according to some aspects. As shown in FIG. 93 ,method 9300 includes selecting a processing function for processingoffload (9302), receiving, from a traffic filter, target data thatoriginates from a local network (9302), applying the processing functionto the target data to obtain processed data (9304), and sending theprocessed data to the local network (9306).

FIG. 94 shows exemplary method 9400 for filtering and routing dataaccording to some aspects. As shown in FIG. 94 , method 9400 includesreceiving signaling that specifies a filter template defining one ormore parameters of target data (9402), applying the filter template toraw data originating from a local network (9404), identifying targetdata from the raw data based on the one or more parameters (9406), androuting the target data to a local server for processing offload (9408).

FIG. 95 shows exemplary method 9500 for execution at a cloud serveraccording to some aspects. As shown in FIG. 95 , method 9500 includesselecting a first processing function for processing offload by a localserver, and selecting a first filter template that defines target datafor the first processing function (9502), sending signaling to the localserver that specifies the first processing function, and sendingsignaling to a traffic filter that specifies the first filter template(9504), selecting an updated processing function or an updated filtertemplate based on one or more dynamic parameters of the processingoffload (9506), and sending signaling to the local server that specifiesthe updated processing function or sending signaling to the trafficfilter that specifies the updated filter template (9508).

FIG. 96 shows exemplary method 9600 for execution at a cloud serveraccording to some aspects. As shown in FIG. 96 , method 9600 includesselecting a processing function for processing offload by a localserver, and selecting a filter template that defines target data for theprocessing function (9602), sending signaling to the local server thatspecifies the processing function, and sending signaling to a trafficfilter that specifies the filter template (9604), and receivingprocessed data from a local server that is based on the filter templateand the processing function (9606).

In one or more further exemplary aspects of the disclosure, one or moreof the features described above in reference to FIGS. 80-89 may befurther incorporated into any of methods 9000-9600.

Computationally-Aware Cell Association

The introduction of small cells into existing mobile broadband networkshas yielded various heterogeneous network (HetNet) architectures. Oneexample is a two-tier heterogeneous network that includes a first tierof macro network access nodes (e.g., macro cells or macro base stations)and a second tier of micro base stations (e.g., small cells, femtocells,home and eNodeBs).

Mobile broadband networks have also begun to incorporate edge computingservices to help support application layer functions. For example,Mobile Edge Computing (MEC) servers can be deployed at or near networkaccess nodes (e.g., co-located with a network access node). These MECservers can add extra processing and/or storage for both terminaldevices and network access nodes to use. For example, a particularterminal device application running at a terminal device can interfacewith a peer application hosted at a MEC server, where the peerapplication may perform processing for the terminal device application.For example, in an uplink case, the terminal device application may senddata to the peer application at the MEC server, which may then performprocessing on the data according to the particular type of application.In a downlink case, the peer application at the MEC server may receivedata (e.g., from a core or internet network) and may process the databefore sending it to the terminal device application. A terminal deviceassociated with a particular network access node can therefore have theco-located MEC server perform application layer processing for its ownterminal device applications.

These terminal device applications may have different data rate andcomputational capacity demands depending on the type of application. Forexample, object recognition algorithms based on cameras and sensors at avehicular terminal device may involve a considerable amount of uplinkdata transfer as well as a large amount of processing. Such applicationsmay therefore have high uplink data rate and computational capacitydemands. Other applications like data sharing applications (e.g., forsharing map or environment data between a fleet of terminal devices) mayhave high uplink and downlink data rate demands but not necessarily havehigh computational capacity demands. Another example is predictiveanalysis algorithms like those used for vehicular collision avoidance,which may have low data rate demands but high computational capacitydemands.

Terminal devices may use the MEC servers co-located with their servingnetwork access node to run the peer application counterpart to itsterminal device application. However, the data rate and computationalcapacities of network access nodes may not be universal in some cases.For example, some network access nodes may have strong channels (e.g.,high SINR) with a given terminal device, and may therefore be able tosupport terminal device applications with higher data rate demands (asthe terminal devices may be able to transfer data to the co-located MECservers at a high rate). Some network access nodes may also beco-located with MEC servers that have higher computational capacity thanothers, and may therefore be better suited to supporting terminal deviceapplications with higher computational capacity demands.

These disparities between the capabilities of network access nodes canarise in any type of network, and can be particularly prominent inheterogeneous networks. For example, in a two-tier heterogeneous networkwith macro and micro network access nodes, macro network access nodesmay be deployed at cell sites with large cabinet areas that can houselarge MEC servers with high computational capacity. In contrast, thesmaller scale of micro network access nodes may limit the size of theirco-located MEC servers, and the macro MEC servers (co-located with macronetwork access nodes) may consequently have greater computationalcapacity than the micro MEC servers (co-located with micro networkaccess nodes). These disparities can also be seen in non-tiered networkcases, or when the various network access nodes in a given tier havedifferent capabilities.

Accordingly, as recognized by this disclosure, there may be certainscenarios where the demands of a terminal device application may makecertain network access nodes (e.g., a certain tier of network accessnodes, or certain individual network access nodes) more suitable for theterminal device application than others. However, the existent cellassociation procedures (i.e., techniques to select which network accessnodes to associate with) focus primarily on radio propagation criteria.For example, some cell association procedures focus on the receivedsignal power (e.g., received signal strength), such as where a terminaldevice is configured to associate with the network access nodecorresponding to the highest received signal power (or, alternatively,the first detected network access node providing a received signal powergreater than a minimum threshold). Accordingly, even if a terminaldevice is executing a terminal device application with certain datarate/computational capacity demands, the cell association procedure mayfail to consider whether network access nodes are co-located with MECservers that can meet the application demands.

Accordingly, some aspects provide a cell association function thatconsiders data rate and computational capacity demands of terminaldevice applications when selecting network access nodes for a terminaldevice to associate with. This can be particularly advantageous in caseswhere MEC servers have different computational capacities, as this mayrender some network access nodes (e.g., co-located with high capacityMEC servers) better choices than others. This cell association functioncan also consider the differing uplink and downlink demands of terminaldevice applications, and can possibly select a different uplink networkaccess node and downlink network access node for the terminal device(e.g., uplink and downlink decoupling). This can be technicallyadvantageous, for example, to provide a radio access connection to aterminal device application that is able to meet its data rate andcomputational capacity demands. This can in turn help reduce or avoidscenarios where a terminal device application suffers from excessivelatency or insufficient data rate.

FIG. 97 shows an exemplary network configuration related to the cellassociation function according to some aspects. As shown in FIG. 97 ,terminal device 9702 (e.g., handheld, vehicular, stationary, or any typeof terminal device) may be running terminal device application 9704(e.g., executed by an application processor of terminal device 9702 aspart of an application layer). Various network access nodes may bewithin the vicinity of terminal device 9702. For example, as shown inFIG. 97 , macro network access node 9706, micro network access node9710, micro network access node 9714, and micro network access node 9718may be located within the vicinity of terminal device 9702. The exampleof FIG. 97 therefore shows a two-tiered network: a first tier of macronetwork access nodes (including macro network access node 9706) and asecond tier of micro network access nodes (including micro networkaccess node 9710, micro network access node 9714, and micro networkaccess node 9718). The number of network access nodes of each shown tierin FIG. 97 is exemplary, and there can be any number of first tiernetwork access nodes (macro network access node) and any number ofsecond tier network access nodes (micro network access nodes, also knownas femtocells). The locations of the first and second tier networkaccess nodes can be respectively obtained by the independent homogeneouspoint-processes Φ_(M) (for macro network access nodes) and Φ_(F) (formicro network access nodes/femtocells). These point processes Φ_(M) andΦ_(F) can be based on the respective density parameters λ_(M) and λ_(F),where density parameter λ_(k) gives the number of tier-k, k={M,F}network access nodes deployed per unit area. While FIG. 97 shows only asingle terminal device, this is only for ease of exposition, and theremay also be a plurality of randomly placed terminal devices withpositions governed by independent homogeneous point process Φ_(U) basedon density parameter λ_(U).

In the example of FIG. 97 , the various first and second tier networkaccess nodes may have co-located MEC servers. In particular, macronetwork access node 9706 may have macro MEC server 9708, micro networkaccess node 9710 may have micro MEC server 9712, micro network accessnode 9714 may have micro MEC server 9716, and micro network access node9718 may have micro MEC server 9720. These MEC servers may be availablefor terminal devices to offload processing for terminal deviceapplications. For example, as shown in FIG. 97 , micro MEC server 9720may host peer application 9722, which may be a counterpart applicationto terminal device application 9704. Accordingly, terminal device 9702may offload processing to micro MEC server 9720, which micro MEC server9720 may perform in the form of peer application 9722. In some aspects,peer application 9722 may be the application layer end point. In someaspects, terminal device application 9704 and host peer application 9722may also be linked with remote application 9728, which may be executedwithin internet network 9726 (to which micro network access node 9718interfaces via core network 9724). In some aspects, macro MEC server9708, micro MEC server 9712, micro MEC server 9716, and micro MEC server9720 may run on top of a virtualized environment, such as together withNetwork Function Virtualization (NFV) functions (e.g., sharing the samecloud resources).

As previously introduced, in some aspects the macro MEC serversco-located with macro network access nodes may have greatercomputational capacity than the micro MEC servers co-located with micronetwork access nodes. For example, the computational capacity (e.g.,total processing power) of macro MEC servers can be denoted as C_(M)(e.g., expressed in CPU cycles/second) while the computational capacityof micro MEC servers can be denoted as C_(F), where C_(M)>C_(F). Thisexample assumes that the computational capacity of macro MEC servers isuniform (e.g., all macro MEC servers have the same computationalcapacity C_(M)) and that the computational capacity of micro MEC serversis likewise uniform (e.g., all micro MEC servers have the samecomputational capacity C_(F)). In some aspects, macro and micro networkaccess nodes may also exhibit other inter-tier disparities, such aswhere the total transmit power P_(M) of a macro network access node isgreater than the total transmit power P_(F) of a micro network accessnode.

In addition to this tiered case that assumes uniform capabilities in agiven tier, there may be other cases where different network accessnodes have different capabilities. For example, in some tiered cases,the network access nodes in a given tier may have different transmitpower and/or computational capacity capabilities. Network access nodesin non-tiered cases may similarly exhibit individual transmit powerand/or computational capacity capabilities.

Depending on the type of application, terminal device application 9704may have certain data rate and computational capacity demands. Forexample, if terminal device application 9704 transmits or receives aconsiderable amount of data, the radio access connection of terminaldevice 9702 may be able to support the data rate demands of terminaldevice 9704 if it has sufficient SINR. Similarly, if terminal deviceapplication 9704 involves a considerable amount of processing (e.g., inthe form of peer application 9722), the MEC server that is hosting peerapplication 9722 may be able to support the computational capacitydemands if it has sufficient computational capacity.

Accordingly, in various aspects, the cell association function thatdecides on cell associations for terminal device 9702 may bias the cellassociation towards a particular network access node over others basedon the relative data rate and computational capacity capabilities of thenetwork access nodes and their co-located MEC hosts, respectively. Inparticular, the cell association function may, for example, use biasvalues (e.g., precomputed bias value obtained by a bias control server,as further detailed below) assigned to the network access nodes thatreflect the capability of the network access nodes to meet the data rateand computational capacity demands of terminal device application 9704.As further described below, the cell association function may use thesebias values to adjust the received powers of the network access nodes asseen at the terminal device (e.g., measured or estimated receivedpower), and may then use the resulting biased received powers to selecta network access node for the terminal device to associate with. As thecell association function uses the bias values as part of the selection,the cell association function can select for association a networkaccess node that can meet an average (e.g., in the spatial deploymentdomain) data rate performance, and that has a MEC server that canprovide an average (e.g., in the spatial deployment domain)computational performance (e.g., in floating point operations per second(FLOPs), hence, satisfying a total processing delay constraint (e.g., inseconds).

FIG. 98 shows an exemplary internal configuration of cell associationcontroller 9800 according to some aspects. Cell association controller9800 may be configured to execute the cell association function andselect target network access nodes for a terminal device to associatewith. In some aspects, cell association controller 9800 may beconfigured to select a single network access node for the terminaldevice to associate with (e.g., to use in both the uplink and downlinkdirections). In some aspects, cell association controller 9800 may beconfigured to select an uplink network access node and a downlinknetwork access node for the terminal device to associate with.

In some aspects, the cell association function may be executed atterminal device 9702. This can be applicable, for example, in cellselection cases, where terminal device 9702 executes the cellassociation function to select a network access node (e.g., a downlinknetwork access node) to camp on during radio idle mode. In theseaspects, terminal device 9702 may be configured in the manner ofterminal device 102 of FIG. 2 , and may therefore include antenna system202, RF transceiver 204, baseband modem 206, application processor 212,and memory 214. As previously described regarding FIG. 2 , protocolcontroller 210 may be configured to handle protocol stack functions forterminal device 102. Accordingly, protocol controller 210 may includecell association controller 9800 as an internal component. When terminaldevice 102 is selecting a network access node to associate with, cellassociation controller 9800 may execute the cell association function(e.g., as part of the terminal device protocol stack) to determine atarget network access node for terminal device 102 to associate with.Protocol controller 210 may then associate with the target networkaccess node (e.g., by camping on the target network access node usingantenna system 202, RF transceiver 204, and digital signal processor 208to receive signals from the target network access node). Applicationprocessor 212 of terminal device 102 may then establish a signalingconnection with the MEC server co-located with the target network accessnode, and may instantiate peer application 9722 at the MEC server.Application processor 212 may then run terminal device application 9704,and may send and receive data with peer application 9722 (running on theco-located MEC server) via the target network access node.

In some aspects, the cell association function can be executed at thenetwork. For example, a network access node or core network node canexecute the cell association function to select a target network accessnode, and can then transmit signaling to terminal device 9702 thatspecifies the target network access node. In an example where the cellassociation function is executed at a network access node, the networkaccess node may be configured in the manner of network access node 110of FIG. 3 . The network access node may therefore include antenna system302, radio transceiver 304, and baseband subsystem 306. In this example,cell association controller 9800 may be an internal component ofprotocol controller 310, and may therefore execute the cell associationfunction as part of the network access node protocol stack. For example,the network access node may initially be serving a particular terminaldevice, such as terminal device 9702. When terminal device 9702eventually becomes eligible for handover to another network access node,cell association controller 9800 may execute the cell associationfunction to select a target network access node for terminal device 9702to handover to. Cell association controller 9800 may then report thetarget network access node to protocol controller 310 of the networkaccess node, which may then send signaling to terminal device 9702 thatidentifies the target network access node. Protocol controller 210 ofterminal device 9702 may receive this signaling and subsequently performa handover to the target network access node.

In an example where the cell association function is executed in thecore network, cell association controller 9800 may be deployed as a corenetwork server. For example, with reference to FIG. 97 , cellassociation controller 9800 may be positioned within core network 9724.Cell association controller 9800 may then execute the cell associationfunction to select target network access nodes for terminal devices tohandover to. In an example where cell association controller 9800selects a target network access node for terminal device 9702 tohandover to, cell association controller 9800 may send signaling toterminal device 9702 (e.g., via a radio access connection provided by anetwork access node) that identifies the target network access node.Protocol controller 210 of terminal device 9702 may receive thissignaling and subsequently perform a handover to the target networkaccess node.

There are therefore different options in terms of the placement of cellassociation controller 9800 in a given network, such as the exemplaryoptions described herein The operation of cell association controller9800 described below is considered applicable for any of these options,regardless of the specific placement of cell association controller9800.

As previously indicated, the cell association function executed by cellassociation controller 9800 may consider the application demands (e.g.,data rate and computational capacity) of terminal device application9704 when considering which target network access nodes to select forterminal device 9702. In particular, when terminal device 9702 isoperating in a multi-tiered heterogeneous network, the nearby networkaccess nodes may have different capabilities based on their tier (e.g.,where the macro tier has a higher computational capacity C_(M) than thecomputational capacity C_(F) of the micro tier), which may rendercertain tiers better for certain terminal device applications thanothers. The cell association function may therefore bias selection ofthe target network access nodes to certain tiers jointly based on thecapabilities of the tiers and the application demands of terminal deviceapplication 9704.

For example, terminal device 9702 may be located at the origin of atwo-dimensional plane, and may be running terminal device application9704. Terminal device 9702 may offload a processing task of c_(UE) CPUcycles to a MEC server (e.g., a macro MEC server or a micro MEC server)in the form of a peer application to terminal device application 9704.As previously indicated, various terminal device applications may havediffering data rate and computational capacity demands based on thespecific type of application. The data rate demands can further bedivided into downlink data rate demands and uplink data rate demands.For example, a particular terminal device application may have certainuplink data rate demands related to the amount of data it transfers inthe uplink direction to the peer application running on a MEC server,and may also have certain downlink data rate demands related to theamount of data it receives in the downlink direction from the peerapplication running on the MEC server. The computational capacitydemands of the terminal device application may relate to the processinglatency of the processing by the peer application.

Accordingly, using the uplink demands as an example, terminal deviceapplication 9704 may be characterized by an uplink SINR demand for datatransmission γ_(UL,th) (e.g., in decibels—(dB)) and a total delay demandt_(delay,th) (e.g., in seconds) related to the execution of theoffloaded task. Further developing this model, the total delay demandcan be expressed as

t _(delay) =t _(delay) ^(exe) +t _(delay) ^(trans)  (1)

where

$t_{delay}^{exe} = \frac{c_{UE}}{\kappa C_{l}}$

(seconds) denotes the time for the peer application (e.g., peerapplication 9722) to execute at a MEC server of tier-l (where l={M,F}for the macro and micro/femtocells), K represents the fraction ofavailable computational resources at the MEC server, and C_(l) (in CPUcycles/second) denotes the computational capacity of the MEC server.Furthermore, t_(delay) ^(trans) represents the radio transmission delay,which can be expressed

$t_{delay}^{trans} = \frac{d_{UE}}{{R_{l,{UL}}R},l,{UL}}$

(seconds) where d_(UE) stands for the number of input bits to betransmitted (e.g., the code to be executed at the MEC server) andR_(l,UL) represents the uplink data rate when terminal device 9702 isassociated with a tier-l network access node (e.g., macro or micronetwork access node).

This uplink data rate R_(l,UL) can further be expressed as

R _(l,UL) =W _(l) log₂(1+γ_(UL,th))Prob{SINR_(l,UL)>γ_(UL,th)}  (2)

where W_(l) (Hertz) denotes the bandwidth allocated to tier-l networkaccess nodes and the probability term Prob{SINR_(l,UL)>γ_(UL,th)} is theprobability with which terminal device 9702 can achieve the targetedSINR demand γ_(UL,th). This probability term is also known as thecoverage probability in various stochastic geometry literatures.

Given these uplink demands γ_(UL,th) and t_(delay,th) of terminal deviceapplication 9704, certain tiers of network access nodes may be bettersuited for terminal device 9702 to be associated with. For example, atier of network access nodes with a dense distribution according todensity parameter λ_(l) may be more likely to have network access nodesthat are proximate to terminal device 9702, which can improve SINR andthus yield a higher data rate. In another example, a tier of networkaccess nodes with a higher transmit power P_(l) may also be able toyield higher SINRs and resulting data rates. Furthermore, a tier ofnetwork access nodes that are co-located with MEC servers with highcomputational capacity C_(l) may be able to better support terminaldevice applications with strict delay demands t_(delay,th).

Accordingly, given these various inter-tier differences, cellassociation controller 9800 may be configured to use precomputed bias tobias the received power of the network access nodes (e.g., the receivedsignal strength from the network access nodes seen at the terminaldevice) in a given tier when considering the network access nodes forassociation. The bias value for a given tier may depend on whether (andto what degree) the capabilities of the network access nodes in the tiermeet the data rate and latency demands of terminal device application9704. Accordingly, a tier with a higher bias value can be considered tobe a better candidate for association than tiers with lower bias values(e.g., may have data rate and/or computational capacity capabilitiesthat are likely to meet the data rate and latency demands of terminaldevice application 9704). Depending on the relative bias values for eachtier, cell association controller 9800 may bias, or ‘weight,’ theselection of a target network access node towards a particular tier. Thebias value B_(l) (dB) for each tier can be precomputed, and thenprovided to cell association controller 9800 for runtime execution ofthe cell association function. This is further described below.

As previously indicated, in some cases there may be individualdisparities between the capabilities of network access nodes (e.g.,within tiers in a tiered case, or between individual network accessnodes in a non-tiered case). Accordingly, cell association controller9800 may be configured, for example, to use precomputed bias values thatare assigned to specific network access nodes, where various networkaccess nodes have different bias values based on their individual datarate and computational capacity capabilities.

This use of the bias values by cell association controller 9800 willtherefore be described first, followed by a description that details howthe bias values can be precomputed. Accordingly, the descriptionimmediately below assumes that the bias values (e.g., per tier, or perindividual network access node) are precomputed and available to cellassociation controller 9800.

As shown in FIG. 98 , cell association controller 9800 may includedistance determiner 9802, biased received power determiner 9804,comparator 9806, and selection controller 9808. In some aspects, thefunctionality of cell association controller 9800 described below may beembodied as executable instructions. Accordingly, distance determiner9802, biased received power determiner 9804, comparator 9806, andselection controller 9808 may each be an instruction set that definestheir respective operations in program code. Cell association controller9800 may therefore be a processor configured to execute each of distancedeterminer 9802, biased received power determiner 9804, comparator 9806,and selection controller 9808. In other aspects, one or more of distancedeterminer 9802, biased received power determiner 9804, comparator 9806,and selection controller 9808 may be separate processors configured toexecute instruction sets that define their respective functionality asprogram code. In other aspects distance determiner 9802, biased receivedpower determiner 9804, comparator 9806, and selection controller 9808may be digital hardware circuitry components that each include digitalhardware logic that defines their respective functionalities.

As previously introduced, cell association controller 9800 may beconfigured to, for a given terminal device, determine target networkaccess nodes for the terminal device (running a terminal deviceapplication) to associate with. For example, cell association controller9800 may be configured to use uplink and downlink bias values todetermine biased uplink and downlink received powers for a plurality ofcandidate network access nodes, and to select an uplink network accessnode and a downlink network access node for the terminal device toassociate with based on the biased uplink and downlink received powers.In some aspects, cell association controller 9800 may also select whichof the uplink and/or the downlink network access node to host the peerapplication on.

FIG. 99 shows exemplary flow chart 9900 according to some aspects, whichillustrates this procedure used by cell association controller 9800 todetermine the target network access nodes for a given terminal device toassociate with. As shown in FIG. 99 , cell association controller 9800may first obtain distance variables and bias values for a plurality ofcandidate network access nodes in stage 9902. In some aspects, thedistance variables may be location information that can be used todetermine the distance between the plurality of candidate network accessnodes and terminal device 9702. For instance, using FIG. 97 as anexample, cell association controller 9800 may receive the locations ofnetwork access nodes 9706, 9710, 9714, and 9718 as the distancevariables of the plurality of candidate network access nodes in stage9902. In some aspects where cell association controller 9800 is locatedin the network (e.g., at a network access node or at a core networkserver), cell association controller 9800 may query a network databasethat stores the locations of network access nodes, which may send thelocations of the plurality of candidate network access nodes to cellassociation controller 9800. In some aspects where cell associationcontroller 9800 is located in a terminal device, e.g., terminal device9702, cell association controller 9800 may request the locations from anetwork database, which may then send the locations to terminal device9702 over the radio access network. In some aspects, the distancevariables may also include the location of terminal device 9702 (whichcan be used to determine the distance between the plurality of candidatenetwork access nodes and terminal device 9702). Accordingly, if cellassociation controller 9800 is located in the network, terminal device9702 may determine and report its position to cell associationcontroller 9800. If cell association controller 9800 is located interminal device 9702, the current position of terminal device 9702 willbe locally available (e.g., by a geo-position sensor of terminal device9702).

In other aspects, the distance variables may be actual radiomeasurements. For example, the distance variables may be received powermeasurements obtained by terminal device 9702 for the plurality ofcandidate network access nodes (e.g., by terminal device 9702 measuringthe received power of signals received from the plurality of candidatenetwork access nodes) and/or may be received power measurements obtainedby the plurality of candidate network access nodes for terminal device9702 (e.g., by the plurality of candidate network access nodes measuringthe received power of signals received from terminal device 9702).Terminal device 9702 and/or the plurality of candidate network accessnodes may obtain these received power measurements and send them to cellassociation controller 9800.

With reference to the bias values that cell association controller 9800receives in stage 9902, in some aspects these bias values may includeuplink and downlink bias values that are assigned to network accessnodes per tier (e.g., per-tier bias values). In other aspects, the biasvalues may include uplink and downlink bias values that are unique toindividual network access nodes (e.g., per-node bias values). Startingwith the per-tier case using the example of FIG. 97 , the bias valuesmay include uplink bias values B_(M,UL)(γ_(UL,th),t_(delay,th)) formacro network access nodes (e.g., network access nodes in the macrotier, including macro network access node 9706), downlink bias valuesB_(M,DL)(γ_(DL,th),t_(delay,th)) for macro network access nodes, uplinkbias values B_(F,UL)(γ_(UL,th),t_(delay,th)) for micro network accessnodes (e.g., network access nodes in the micro tier, including micronetwork access nodes 9710, 9714, and 9718), and downlink bias valuesB_(F,DL)(γ_(DL,th),t_(delay,th)) for micro network access nodes. Asdenoted by the data rate and latency demands γ_(DL,th)/γ_(UL,th) andt_(delay,th) in the parentheses, the uplink and downlink bias values maybe precomputed specifically based on the application demands of terminaldevice application 9704. These parentheses terms are dropped in thefollowing description for simplicity.

Accordingly, when cell association controller 9800 executes the cellassociation function for another terminal device application (e.g., forterminal device 9702, or for another terminal device that is running adifferent terminal device application with different data rate andlatency demands), the bias values may be different. For example, if theother terminal device application has higher uplink data rate demandsthan terminal device application 9704, the uplink bias values used bycell association controller 9800 may be higher for tiers of networkaccess nodes that have higher data rate capabilities (and vice versa fortiers of network access nodes that have lower data rate capabilities).These differences in bias values may likewise hold for terminal deviceapplications with lower uplink data rate demands, terminal deviceapplications with higher/lower downlink data rate demands, and terminaldevice applications with higher/lower latency demands. In such cases,the uplink and downlink bias values used by cell association controller9800 may be relatively higher for network access nodes that arebetter-suited to support the terminal device application than fornetwork access nodes that are lesser-suited to support the terminaldevice application.

In this per-tier case, it may be assumed that all of the network accessnodes in a given tier (e.g., located anywhere, or all of the networkaccess nodes in particular tier that are located within a specificgeographic area) have uniform data rate and computational capacitycapabilities, and therefore have the same uplink and downlink biasvalues (e.g., the network access nodes in the macro tier all have biasvalues B_(M,DL) and B_(M,UL), and the network access nodes in the microtier all have bias values B_(F,DL) and B_(F,UL)). While the bias valueswithin a given tier are the same, different tiers may be assumed to havedifferent capabilities, and thus have different bias values. This can beexpanded to other cases where there are more than two-tiers, and thenetwork access nodes in each tier likewise have uniform uplink anddownlink bias values. The bias values may therefore be based on thecapability of the network access nodes in each tier to meet the datarate and latency demands of the terminal device application (e.g., tosupport the terminal device application by running the peerapplication).

In contrast, in the per-node case, network access nodes may haveindividual bias values. For example, a first network access node of theplurality of candidate network access nodes may have bias valuesB_(1,UL) and B_(1,ULDL), a second network access node of the pluralityof candidate network access nodes may have bias values B_(2,UL) andB_(2,ULDL), a third network access node of the plurality of candidatenetwork access nodes may have bias values B_(3,UL) and B_(3,ULDL), andso forth. This can be the case where, for example, there are not anytier assignments, or where there are tier assignments but the data rateand computational capabilities are not uniform across the network accessnodes of each tier. The individual bias values assigned to each givencandidate network access node may, therefore, be based on the individualdata rate and computational capacities of the candidate network accessnode to meet the data rate and latency demands of the terminal deviceapplication (e.g., to support the terminal device application).

In either case of per-tier or per-node bias values, each of theplurality of candidate network access nodes may correspond to specificbias values. For example, each candidate network access node may eitherbelong to a particular tier to which bias values are uniformly assignedor may be individually assigned bias values unique to the candidatenetwork access node. Accordingly, in either case cell associationcontroller 9800 may be able to identify the uplink and downlink biasvalues for any particular candidate network access node.

Cell association controller 9800 may use this information obtained instage 9902 as input data for the cell association function. As shown inFIG. 98 , distance determiner 9802 may receive the distance variables ofthe terminal device and the plurality of candidate network access nodesas its input while biased received power determiner 9804 may receive theuplink and downlink bias values as its input. Then, in stage 9904,distance determiner 9802 may determine the distances between theplurality of candidate network access nodes and the terminal devicebased on the distance variables. For example, if the distance variablesinclude locations of terminal device 9702 and the plurality of candidatenetwork access nodes, distance determiner 9802 may perform a two-pointdistance calculation using the location of the terminal device and eachof the plurality of candidate network access nodes in stage 9904, andobtain the distance between the terminal device and each of theplurality of candidate network access nodes. Using the example of FIG.97 , distance determiner 9802 may determine the distance betweenterminal device 9702 and each of network access nodes 9706, 9710, 9714,and 9718. In another example, if the distance variables include radiomeasurements such as received power measurements (e.g., RSSI), distancedeterminer 9802 may be configured to determine the distance betweenterminal device 9702 and the plurality of candidate network access nodesby estimating the distance based on the received power measurements(e.g., using a free-space pathloss model to estimate a distance based ona received power).

Distance determiner 9802 may then provide the distances to biasedreceived power determiner 9804. As shown in FIG. 98 , biased receivedpower determiner 9804 may also receive the uplink bias values anddownlink bias values for the plurality of candidate network access nodes(e.g., per-tier or per-node bias values). Biased received powerdeterminer 9804 may then be configured to determine biased receivedpowers for the plurality of candidate network access nodes for uplinkand downlink in stage 9906.

For example, in some aspects, biased received power determiner 9804 maybe configured to determine a biased receive power for each of theplurality of candidate network access nodes for the uplink and downlink.For example, for a given candidate network access node n, biasedreceived power determiner 9804 may identify its uplink bias valueB_(n,UL) and downlink bias value B_(n,DL). The bias values B_(n,UL) andB_(n,DL) can be either a per-tier bias value (that is uniform acrossnetwork access nodes in a tier to which the candidate network accessnode n) or a per-node bias value (that is unique to the candidatenetwork access node n). Biased received power determiner 9804 may thendetermine a biased downlink received power for the candidate networkaccess node by calculating B_(n,DL)∥x*∥^(−α), where α is the pathlosscoefficient (e.g. α=3.8 or 4 for free-space propagation), ∥x*∥ is thedistance between the candidate network access node and terminal device9702 (assuming terminal device 9702 is at the origin and x gives theposition of the candidate network access node on a two-dimensionalplane, e.g., where x∈Φ_(k) is a point x of a tier-k network access nodeis located in a tiered case), and B_(n,DL) is the shortened version ofdownlink bias value B_(n,DL)(γ_(DL,th),t_(delay,th)) that is based onthe downlink data rate demand γ_(DL,th) and the latency demandt_(delay,th) of terminal device application 9704. The term ∥x*∥^(−α) maytherefore represent the received signal power (e.g., an estimatedreceived signal power), and multiplying the received signal power by thebias value B_(n,DL) may therefore yield a biased received signal power.Biased received power determiner 9804 may likewise determine a biaseduplink received power for the candidate network access node bycalculating B_(n,UL)∥x*∥^(−α) using the uplink bias value B_(n,UL)(short for B_(n,UL)(γ_(UL,th),t_(delay,th))).

After determining the biased uplink and downlink received powers for theplurality of candidate network access nodes in stage 9906, biasedreceived power determiner 9804 may provide the biased uplink anddownlink received powers to comparator 9806. Comparator 9806 may then,in stage 9908, compare the biased uplink and downlink received powers toidentify a maximum biased uplink received power and a maximum biaseddownlink received power. Comparator 9806 may perform this separately foruplink and downlink. For example, the comparator may compare the biaseduplink received powers for the plurality of candidate network accessnodes to identify a maximum biased uplink received power, and separatelycompare the biased downlink received powers for the plurality ofcandidate network access nodes to identify a maximum downlink biasedreceived power.

After identifying the maximum biased uplink received power and themaximum biased downlink receive power, comparator 9806 may specify themaximum biased uplink and downlink received powers to selectioncontroller 9808. Selection controller 9808 may then in stage 9910 selectthe candidate network access node corresponding to the maximum biaseduplink received power as an uplink network access node for terminaldevice 9702 to associate with, and in stage 9912 select the candidatenetwork access node corresponding to the maximum biased downlinkreceived power as a downlink network access node for terminal device9702 to associate with.

In some aspects, selection controller 9808 may then send controlsignaling to terminal device 9702 or to the radio access network (e.g.,to a current serving network access node) that indicates the uplink anddownlink network access nodes. Terminal device 9702 may then connectwith the uplink and downlink network access nodes (e.g., via reselectionor handover in coordination with the radio access network). Terminaldevice 9702 may subsequently instantiate peer application 9722 at theuplink and/or downlink network access nodes, and terminal deviceapplication 9704 may begin transmitting or receiving data with peerapplication 9722 via the uplink and/or downlink network access nodes.

The above description for FIGS. 98 and 99 can generally apply forper-tier and per-node bias values. In particular, as biased receivedpower determiner 9804 can determine which uplink and downlink bias valuecorresponds to each of the plurality of candidate network access nodes,biased received power determiner 9804 can identify the appropriate biasvalues for use in determining the biased uplink and downlink receivedsignal powers (e.g., by multiplying the received signal power (derivedfrom the distance) by the bias value). Comparator 9806 may then comparethe biased uplink received powers for each candidate network access nodeto identify a maximum uplink received power, and to compare the biaseddownlink received powers for each candidate network access node toidentify a maximum downlink received power.

In some aspects where per-tier bias values are used, cell associationcontroller 9800 may alternatively be configured to use specialized logicto select the uplink and downlink network access nodes. In particular,as the network access nodes in a given tier will share the same biasvalue (e.g., for uplink and downlink), the candidate network access nodewith the shortest distance to terminal device 9702 will have the highestbiased received powers (e.g., in downlink and uplink, as the receivedpower term ∥x*∥^(−α) will be the highest in the tier while the biasvalues will be the same).

Accordingly, in some aspects cell association controller 9800 may beconfigured to identify the candidate network access node in each tierwith the shortest distance, determine the biased uplink and downlinkreceived powers for these candidate network access nodes (e.g.,determine the biased uplink and downlink received powers only for thesecandidate network access nodes), and then identify the uplink anddownlink network access nodes from these biased uplink and downlinkreceived powers.

FIG. 100 shows exemplary flow chart 10000 according to some aspects,which illustrates an example of this specialized logic. Likewise to thecase of flow chart 9900 in FIG. 99 , cell association controller 9800may be configured to execute the procedure of flow chart 10000 as partof the cell association function. As shown in FIG. 100 , distancedeterminer 9802 may obtain distance variables for the plurality ofcandidate network access nodes and biased received power determiner 9804may obtain bias values for the plurality of network access nodes instage 10002. As this is a per-tier case, each tier of network accessnodes may have an uplink bias value and a downlink bias value (e.g.,that is shared between all network access nodes of a given tier).Accordingly, in some aspects biased received power determiner 9804 mayobtain an uplink bias value and a downlink bias value for each tier instage 10002.

Distance determiner 9802 may then determine distances between theplurality of candidate network access nodes and terminal device 9702based on the distance variables in stage 10004. Distance determiner 9802may perform stage 10004 in the same manner described above for stage9904.

Distance determiner 9802 may then, in stage 10006, identify thecandidate network access node in each tier that is at the shortestdistance from terminal device 9702 as a benchmark network access node.As distance determiner 9802 performs this for each tier, distancedeterminer 9802 may identify one candidate network access node as abenchmark network access node per tier. For example, using point processΦ_(k) for the positions x of network access nodes in a given tier-k,distance determiner 9802 may be configured to identify

$\underset{x \in \Phi_{k}}{\min}{x}\left( {{e.g.},} \right.$

the network access node location x in Φ_(k) with the shortest distanceto location of terminal device 9702 at the origin). Distance determiner9802 may then take the candidate network access node for tier-k withposition x satisfying

$\underset{x \in \Phi_{k}}{\min}{x}$

as the benchmark network access node for tier-k. Distance calculator9802 may then provide the distances for the benchmark network accessnodes to biased received power determiner 9804 (and, for example, maynot provide to comparator 9806 distances for the remaining candidatenetwork access nodes that are not benchmark network access nodes).

Biased received power determiner 9804 may then determine biased uplinkand downlink received powers for the benchmark network access nodes instage 10008. Biased received power determiner 9804 may perform stage10008 in the same manner described above for stage 9906. For example,for each benchmark network access node, biased received power determiner9804 may identify which tier it belongs to, identify the uplink anddownlink bias values for the tier, and determine a biased uplink anddownlink received power based on the uplink and downlink bias values andthe distance between the benchmark network access node and terminaldevice 9702. For example, biased received power determiner 9804 maydetermine the uplink biased receive power by calculatingB_(k,UL)∥x*∥^(−α) using the uplink bias value B_(k,UL) for tier-k towhich the benchmark candidate network access belongs and position x* ofthe benchmark network access node, and may determine downlink biasedreceive power by calculating B_(k,DL)∥x*∥^(−α) using the downlink biasvalue B_(k,DL) for tier-k and position x* of the benchmark networkaccess node.

Biased received power determiner 9804 may then provide the biased uplinkand downlink received powers for the benchmark network access nodes tocomparator 9806. Comparator 9806 may then in stage 10010 compare thebiased received powers and identify a maximum biased uplink receivedpower and a maximum biased downlink received power. Comparator 9806 mayprovide these identified maximum biased uplink and downlink receivedpowers to selection controller 9808. Selection controller 9808 may thenselect the candidate network access node (a benchmark network accessnode) corresponding to the maximum biased uplink received power as anuplink network access node for terminal device 9702 to associate with instage 10012, and may also select the candidate network access node (abenchmark network access node) corresponding to the maximum biaseddownlink received power as a downlink network access node for terminaldevice 9702 to associate with in stage 10014.

Selection controller 9808 may then notify terminal device 9702 and/orthe radio access network of the uplink and downlink network access nodes(e.g., by sending control signaling). Terminal device 9702 may then beable to connect to the uplink and downlink network access nodes andbegin using their co-located MEC servers to host the peer application toterminal device application 9704.

Accordingly, even though a particular candidate network access node maybe located closest to terminal device 9702 (e.g., have the smallest 114and thus the highest received signal power ∥x∥^(−α)), it may belong to atier that has a lower bias value than other tiers (e.g., as the networkaccess nodes of the other tiers may have data rate and/or computationalcapacity capabilities that better meet the application demands ofterminal device application 9704) or may have a per-node bias value thatis lower than those for other candidate network access nodes. Dependingthe case-specific distances and bias values, cell association controller9800 can therefore ultimately select another candidate network accessnode as the uplink or downlink network access node (e.g., if the othercandidate network access node has a bias value that causes its biaseduplink or downlink received power to be larger).

Cell association controller 9800 may therefore bias selection of uplinkand downlink network access nodes towards certain tiers and/orindividual network access nodes that are better suited to support aparticular terminal device application (e.g., that have data rate and/orcomputational capacity capabilities that meet the data rate and/orlatency demands of the terminal device application). As previouslyindicated, the bias values may be precomputed for specific terminaldevice applications. In some cases, this biasing many enable cellassociation controller 9800 to select uplink and downlink network accessnodes that meet the data rate and/or latency demands of the terminaldevice application. This may improve performance, as the terminal devicemay be able to run the terminal device application with a reducedprobability of violating data rate and/or latency demands.

In a variation of flow chart 9900, in some aspects biased received powerdeterminer 9804 may determine the biased uplink and downlink receivedpowers based on actual received power measurements. For example, aspreviously indicated, in some aspects the distance variables may includeradio measurements, such as received power measurements performed byterminal device 9702 for the plurality of candidate network access nodesor performed by the plurality of candidate network access nodes forterminal device 9702. Instead of estimating the distance based on thereceived power measurement and then determining a biased received powerbased on the estimated distance, distance calculator 17102 may providethe received power measurements to biased received power determiner9804. Biased received power determiner 9804 may then determine thebiased uplink and downlink received powers by applying the uplink anddownlink bias values to the received power measurements. Cellassociation controller 9800 may use these biased uplink and downlinkreceived powers in the same manner described above.

The below pseudocode describes a non-limiting example of the cellevaluation function in the uplink direction as executed cell associationcontroller 9800. This example may relate to a per-node case, such aswhere individual network access nodes have unique biasvalues/capabilities. As this is the uplink direction, the uplink biasvalues B_(l,UL) are used. Cell association controller 9800 can executesimilar pseudocode for the downlink direction by using the downlink biasvalues B_(l,DL)

 Input: γ_(th), t_(delay,th), // Parameters characterizing the QoS classN₁, N₂, // Number of network access nodes for tier-1 and tier-2 at agiven  area C₁, C₂ // Computational capacity of a M-MEC and a m-MECserver,  respectively Output: Index of associated network access node(macro or micro) 1. Compute {B_(1,UL), B_(2,UL)} // Design bias valuesfor the two tiers which are QoS  //class-dependent and computationalcapacity-aware 2  Compute distances {x_(j,I)}, I=1,2, j=1,..., N_(I) //These distances coincide with the  //locations of the network accessnodes as the terminal  //device is assumed to be located at the origin(0,0) 3. Assoc_BS := 0; // Initialization 4. For (I=1:2) // Tier index5. For (j=1:N_(I)) // Index of network access node belonging to tier-I6.  x* := x_(j,I); // x* refers to the distance between terminal deviceand the    //focused network access node 7.  If (CellRule( ) is true)then //cell association criterion focusing     //on the j-th networkaccess node of   //tier-I (BS_(j,I)) 8.    Assoc_BS := BS_(j,I); 9.   break; // Once criterion CellRule( ) is satisfied the “best” //accessnode for association is found 10.  End_if 11. End_for 12. End_for 13. If(Assoc_BS == 0) then 14. Outage := true;   //Because of either low BSdeployment densities and/or //due to excessive QoS requirements γ_(th)and t_(delay,th).  //In other words, no MBS and no FBS will be able to//satisfy the QoS requirements 15. End_ifwhere the function CellRule( ) refers to the cell evaluation ruleexpressed as

$\begin{matrix}{{{B_{l,{DLUL}}\left( {\gamma_{{DLUL},{th}},t_{{delay},{th}}} \right)}{x^{*}}^{- \alpha}} \geq {{B_{k,{DLUL}}\left( {\gamma_{{DLUL},{th}},t_{{delay},{th}}} \right)}\left\{ {\underset{x \in \Phi_{k}}{\min}{x}} \right\}^{- \alpha}}} & (3)\end{matrix}$

The below pseudocode shows another non-limiting example of the logicthat cell association controller 9800 can use to identify an uplinkand/or downlink network access node for terminal device 9702 toassociate with.

Input: N //number of network access nodes  B_(n) //vector of bias valuesfor each network access node BS_(n), n=1:N  X_(n) // vector of distancesbetween terminal device and network access nodes  P // initial benchmarkbiased receive power (can be set to zero, or set to a minimum  // value)Assoc_BS = 0 //initialize network access selection to null For n=1:N//loop over each of the N network access nodes if(B_(n)||X_(n)||{circumflex over ( )}(−alpha) >= P) //check if biasedreceived power for focused network access   //node is greater thanbenchmark biased receive power     Assoc_BS=B_(n) //if so, set thecurrent value of the selected network access node     //to be thefocused network access node     P= B_(n)||X_(n)||{circumflex over( )}(−alpha) //set the biased receive power for the focused network   //access node as the new benchmark biased receive power.        //Thebiased received power for the next focused network     //access nodewill therefore be compared to this value  end if End for If (Assoc_BS ==0) //check if any network access nodes were selected  Outage = true//when P is initialized to some minimum value, and none of the //candidate BSs have biased receive power that is bigger than P,      //Assoc_BS will be null. The function can then declare an outageevent,    //as not network access node had sufficient transmit power.Conversely,   //if any candidate network access node has biased receivepower bigger //than P, it will be set as the new selected network accessnode (in the           //loop) End If

As shown above, this pseudocode may initialize a benchmark biasedreceived power P, which can be set to 0 or to another desired minimumvalue. The pseudocode may then loop over each candidate network accessnode and determine its biased received power based on its individualbias value. The pseudocode may then compare its biased received power toP. If the focused network access node has biased received power greaterthan or equal to P, the pseudocode may store the focused network accessnode as the selected network access node and store its biased receivedpower as the new P. Once the pseudocode loops through all candidatenetwork access nodes, it can check whether any candidate network accessnode is stored as the selected network access node (e.g., whether anycandidate network access node had biased received power greater than P).If so, this selected network access node will be the candidate networkaccess node with the highest biased received signal power. If not, thepseudocode can declare an outage event, as no candidate network accessnode had biased received power greater than P.

FIGS. 101-103 show several different examples according to variousaspects that illustrate execution of the cell association function bycell association controller 9800. These examples relate to the scenarioof FIG. 97 , where terminal device 9702 is executing terminal deviceapplication 9704 with peer application 9722 that is executed on a MECserver co-located with a network access node. Using uplink as an example(that can likewise be applied for downlink), cell association controller9800 may select an uplink network access node for terminal device 9702to associate with. This uplink network access node will therefore hostpeer application 9722. These examples assume a per-tier case, whereuplink bias values B_(M,UL) and B_(F,UL) (for macro network access nodesand micro network access nodes, respectively) have been pre-computedbased on the uplink data rate demands γ_(UL,th) and latency demandst_(delay,th) of terminal device application 9704 (as further describedlater).

Starting with FIG. 101 , terminal device application 9704 may have 1) ashort amount of input data d_(UE) for remote application execution aspeer application 9722, and 2) a large number of computational operationsc_(UE) (e.g., a demanding computational task). As previously describedfor FIGS. 98-100 , cell association controller 9800 may determine biaseduplink received power for macro network access node 9706 and micronetwork access nodes 9710, 9714, and 9718. Cell association controller9800 may use the uplink bias value B_(M,UL) for tier-M for macro networkaccess node 9706 and uplink bias value B_(F,UL) for tier-F micro networkaccess nodes 9710, 9714, and 9718.

The coverage areas shown in FIG. 101 are depicted as biased coverageareas that scale with the biased received signal power. The size of thebiased coverage areas is therefore an exemplary visual representation ofthe biased received signal powers of the various network access nodes.Accordingly, as shown in FIG. 101 , macro network access node 9706 mayhave a large uplink bias value B_(M,UL) (e.g., due to the largecomputational capacity enough to satisfy the latency demand of terminaldevice application 9704), and this may result to a large biased coveragearea and biased received signal powers. Micro network access nodes 9710,9714, and 9718 may have smaller uplink bias values B_(F,UL), and thusmay have smaller biased coverage areas and biased received signalpowers. Accordingly, as shown in FIG. 101 , terminal device 9702 mayfall within the biased coverage area of macro network access node 9706but not within the biased coverage areas of any of micro network accessnodes 9710, 9714, and 9718.

After determining the biased uplink coverage areas, cell associationcontroller 9800 may evaluate the plurality of candidate network accessnodes, e.g., candidate network access nodes 9706, 9710, 9714, and 9718.Accordingly, cell association controller 9800 may identify which ofcandidate network access nodes 9706, 9710, 9714, and 9718 has thelargest biased uplink received signal power.

In the case of FIG. 101 , macro network access node 9706 may have thelargest biased uplink received signal power. Cell association controller9800 may therefore select macro network access node 9706 as the uplinknetwork access node for terminal device 9702 to associate with. Cellassociation controller 9800 may also perform a similar evaluation in thedownlink direction to select a downlink network access node.

Continuing to the example of FIG. 102 , terminal device application 9704may have a considerable amount of input data d_(UE) to send forexecution by peer application 9722. However, the computational capacitydemands c_(UE) of peer application 9722 may be relatively small (e.g., alightweight computational task). Compared to the example of FIG. 101 ,the uplink bias values B_(M,UL) and B_(F,UL) may be less biased towardsmacro network access nodes (e.g., as computational capacity is a lessimportant resource for satisfying the latency demand of terminal deviceapplication 9704 whereas the uplink data rate is more important towardssatisfying such demand).

Accordingly, as shown by the biased coverage areas depicted in FIG. 102, terminal device 9702 may be located within the biased coverage area ofmicro network access node 9718 but outside of the biased coverage areasof macro network access node 9706 and micro network access nodes 9710and 9714. Given the positioning shown in FIG. 102 and the previouslyintroduced relationship between biased received power and depictedbiased coverage area, cell association controller 9800 may thereforedetermine that micro network access node 9718 has the highest biaseduplink received power. Cell association controller 9800 may thereforeselect micro network access node 9718 as the uplink network access nodefor terminal device 9702 to associate with.

According to the example of FIG. 102 , there may be a considerableamount of input data d_(UE) and a small computational capacity demandc_(UE). However, as shown in FIG. 103 the density of macro and micronetwork access nodes may not be sufficient for terminal device 9702 tobe located within the biased coverage area of any network access node.As terminal device 9702 is only closest to the biased coverage area ofmicro network access node 9718, cell association controller 9800 maydetermine that none of macro network access node 9706, micro networkaccess node 9710, or micro network access node 9714 have high enoughbiased received power to meet the data rate and/or computationalcapacity demands of terminal device application 9704. For example,selection controller 9808 may be configured to compare the maximumbiased uplink received power to a biased received power threshold. Ifthe maximum biased uplink received power is less than the biasedreceived power threshold, selection controller 9808 may be configured todeclare an outage event, as no candidate network access node may have abiased uplink received power that is greater than the biased receivedpower threshold. Accordingly, while micro network access node 9718 mayhave the maximum biased uplink received power and may be the preferrednetwork access node for association, cell association controller 9800may declare an outage event due to the QoS violation.

The examples illustrated above describe various aspects related touplink and downlink decoupling, namely, where cell associationcontroller 9800 may be configured to select an uplink network accessnode and a downlink network access node based on the biased receivedpowers. In some cases (depending on the distance variables and biasvalues), cell association controller 9800 may be configured to selectthe same network access node as both the uplink and downlink networkaccess node. In these cases, terminal device 9702 may therefore use thesame network access node for both uplink and downlink communications.

Additionally, as there is only one network access node, terminal device9702 may use the MEC server co-located with the network access node tohost peer application 9722. Accordingly, terminal device application9704 may send uplink data to peer application 9722 by sending it to thenetwork access node over the uplink channel, and may receive downlinkdata from peer application 9722 by receiving it from the network accessnode over the downlink channel.

This case where there is only one network access node is a special casewithin the more general context of uplink and downlink decoupling.Accordingly, in other cases, cell association controller 9800 may selectdifferent network access node as the uplink and downlink network accessnodes. There may therefore be two options for hosting peer application9722: in the MEC server co-located with the uplink network access node,or in the MEC server co-located with the downlink network access node.

In some aspects, cell association controller 9800 may be configured toselect which MEC server to host peer application 9722 at, namely betweenthe MEC server co-located with the uplink network access node (theuplink MEC server) and the MEC server co-located with the downlinknetwork access node (the downlink MEC server). In other aspects, cellassociation controller 9800 may be configured to select the uplink anddownlink network access nodes and allow terminal device 9702 to decidewhich MEC server to use.

In aspects where cell association controller 9800 is configured toselect the MEC server for hosting peer application 9722, selectioncontroller 9808 may be configured to handle the selection. Accordingly,after selecting the uplink and downlink network access node (e.g., instages 9910-9912 and 10012-10014 of FIGS. 99 and 100 ), selectioncontroller 9808 may select to host peer application 9722 at either theuplink MEC server or the downlink MEC server.

In some aspects, selection controller 9808 may be configured to use adownlink-to-uplink traffic ratio (DL/UL traffic ratio) to decide whetherto host peer application 9722 at the uplink MEC server or the downlinkMEC server. For example, when the average DL/UL traffic ratio is greaterthan 1 (i.e., there is more downlink than uplink traffic, e.g., greaterthan 1.1), it can be advantageous for peer application 9722 be executedat the downlink MEC server (co-located with the downlink network accessnode). Conversely, when the average DL/UL traffic ratio is less than 1(e.g., there is more uplink than downlink traffic), it can beadvantageous for peer application 9722 to be executed at the uplink MECserver (co-located with the uplink network access node). In anotherexample, when the average DL/UL traffic ratio is around 1, it can beadvantageous to run two instances of peer application 9722 at both MECservers co-located with the downlink and uplink network access nodes.

Accordingly, cell association controller 9800 may also be configured toselect the MEC server for hosting peer application 9722 based on theDL/UL traffic ratio. As indicated above, selection controller 9808 maybe configured to determine whether the average DL/UL traffic ratio ofterminal device application 9704 is greater than 1 (e.g., greater than1.1), less than 1 (e.g., less than 0.9), or about 1 (e.g., between 0.9and 1.1). If selection controller 9808 determines that the average DL/ULtraffic radio is greater than 1 (or, e.g., greater than 1.1), selectioncontroller 9808 may select the downlink MEC for hosting peer application9722. Selection controller 9808 may then instruct terminal device 9702and/or the downlink network access node (e.g., by sending controlsignaling) to host peer application 9722 at the downlink MEC server.

If selection controller 9808 determines that the average DL/UL trafficratio is less than 1 (or, e.g., less than 0.9), selection controller9808 may select the uplink MEC server for hosting peer application 9722.Selection controller 9808 may then instruct terminal device 9702 and theuplink network access node (e.g., by sending control signaling) to hostpeer application 9722 at the uplink MEC.

If selection controller 9808 determines that the average DL/UL trafficratio is about 1 (e.g., between 0.9 and 1.1), selection controller 9808may select both the downlink and uplink MEC servers for hosting peerapplication 9722. Selection controller 9808 may then instruct terminaldevice 9702 and both the downlink and uplink network access nodes (e.g.,by sending control signaling) to host peer application 9722 at both thedownlink and uplink MEC servers

FIGS. 104-106 show several examples of hosting peer application 9722 atthe downlink and/or uplink MEC servers. In the example of FIG. 104 ,cell association controller 9800 may select network access node 10402(e.g., either macro or micro, depending on the results of the cellevaluation function) as the uplink network access node and may selectnetwork access node 10406 as the downlink network access node. Cellassociation controller 9800 may also determine that the DL/UL trafficratio is about 1 (e.g., between 0.9 and 1.1), and may therefore selectfor both MEC server 10404 (the uplink MEC server, i.e., co-located withuplink network access node 10402) and MEC server 10408 (the downlink MECserver, i.e., co-located with downlink network access node 10406) tohost peer application 9722. Accordingly, as shown in FIG. 104 , MECserver 10404 may host a first instance of peer application 9722 whileMEC server 10408 may host a second instance of peer application 9722.Terminal device application 9704 running at terminal device 9702 maytherefore transmit uplink data (on an application-layer connection) touplink network access node 10402, which the first instance of peerapplication 9722 running at MEC server 10404 may process in the uplinkdirection. In the downlink direction, MEC server 10408 may transmitdownlink data addressed to terminal device application 9704, and thesecond instance of peer application 9722 running at MEC server 10408 mayprocess the downlink data. The second instance of peer application 9722may then send the resulting data to terminal device application 9704running on terminal device 9702.

In the example of FIG. 105 , the cell association controller maysimilarly select network access node 10402 as the uplink network accessnode and network access node 10406 as the downlink network access node.However, the DL/UL ratio may be less than 1 (e.g., terminal deviceapplication 9704 may be uplink-only, or may involve more uplink trafficthan downlink traffic). Accordingly, cell association controller 9800may instruct MEC server 10404 (the uplink MEC server) to host peerapplication 9722. Terminal device application 9704 running at terminaldevice 9702 may therefore send uplink data to network access node 10402,and peer application 9722 running at MEC server 10404 may process theuplink data. In cases where the resulting data is used at terminaldevice application 9704, peer application 9722 may either 1) send theresulting data to an external server, such as one running remoteapplication 9728, which may then send the resulting data to terminaldevice application 9704 via network access node 10406, or 1) if there isa direct interface between network access node 10402 and network accessnode 10406, send the resulting data directly to network access node1046010406 over the direct interface, which may then transmit theresulting data to terminal device 9702.

In the example of FIG. 106 , cell association controller 9800 maysimilarly select network access node 10402 as the uplink network accessnode and network access node 10406 as the downlink network access node.However, the DL/UL ratio may be greater than 1 (e.g., terminal deviceapplication 9704 may be downlink-only, or may involve more downlinktraffic than uplink traffic). Accordingly, cell association controller9800 may instruct MEC server 10408 (the downlink MEC server, e.g.,co-located with network access node 10406) to host peer application9722. Accordingly, peer application 9722 may process downlink data forterminal device application 9704, and network access node 10406 may thensend the downlink data to terminal device 9704.

As previously indicated, the bias values for various tiers and/or forindividual network access nodes can be designed to reflect theircapability to meet the data rate and latency demands of terminal deviceapplication 9704. For example, a bias control server can be deployed inthe network that can calculate the bias values for cell associationcontroller 9800 to use for execution of the cell association function.FIG. 107 shows an exemplary internal configuration of bias controlserver 10700 according to some aspects. Bias control server 10700 may bedeployed for example, as part of the core network, part of a MEC server,or part of an external cloud/internet server. Bias control server 10700may be configured to compute bias values, such as by computing the biasvalues offline (e.g., for later use for cell association controller9800) and/or by updating the bias values over time (e.g., and providingthe updated bias values B_(l) to cell association controller 9800).

As shown in FIG. 107 , bias control server 10700 may include input datamemory 10702 and bias processor 10704. Input data memory 10702 may be amemory configured to collect input parameters relevant to the biasvalues, and to provide the input parameters to bias processor 10704.Bias processor 10704 may be a processor configured to execute programcode that defines computation of the bias values. This functionality isdescribed in full below.

FIG. 108 shows flow chart 10800 according to some aspects, whichdescribes calculation of bias values by bias control server 10700. Aspreviously indicated, bias values may be precomputed based on a specificterminal device application (e.g., based on the particular uplink anddownlink data rate and latency demands of the terminal deviceapplication). Accordingly, flow chart 10800 describes a procedure forcalculating bias values for a given terminal device application. Biascontrol server 10700 can therefore calculate bias values tailored fordifferent terminal device applications by executing flow chart 10800multiple times with different data rate and latency demands for thedifferent terminal device applications.

The following example uses calculation of uplink bias values forterminal device application 9704. Bias control server 10700 may use thesame procedure for calculation of downlink bias values using inputparameters that relate to the downlink demands of terminal deviceapplication 9704. As shown in FIG. 108 , input data memory 10702 mayfirst collect parameters relevant to the bias values in stage 10802. Forexample, input data memory 10702 may collect first parameters aboutuplink data rate and computational capacity demands of terminal deviceapplication 9704, and may collect second parameters about capabilitiesof network access nodes. For example, the first parameters can includethe QoS requirements (e.g., data rate, latency) associated with terminaldevice application 9704. For example, terminal device application 9704may be pre-assigned to a certain QoS class (e.g., such as a QoS ClassIndicator (QCI) in LTE or Type of Service (TS) and DifferentiatedServices Code Point (DSCP) fields in IP). This QoS class may havepredefined QoS requirements, and may therefore indicate an uplink datarate or SINR demand γ_(th) (e.g., in downlink and/or uplink) and/or atask completion latency t_(delay,th) Input data memory 10702 may alsocollect information about the amount of uplink data to be offloaded,d_(UE) (e.g., as in FIGS. 101-103 ), which may be relevant to the datarate demands. Input data memory 10702 may collect such first parametersin stage 10802, such as by receiving QoS information from a core networkserver.

Input data memory 10702 may also collect, for example, second parametersthat relate to information about the deployment densities of networkaccess nodes in each tier in stage 10802. This can apply for a per-tiercase. For example, as previously introduced, the network access nodes ina given tier-l may be distributed according to a given point processΦ_(l) that is based on a density parameter γ_(l). Input data memory10702 may collect this density information for each tier, such as byreceiving this information from a core network server or other locationthat stores information about the deployments of network access nodesfor a given network.

Input data memory 10702 may collect second parameters about thecomputational capacities of the MEC servers co-located with the networkaccess nodes in stage 10802. If for a per-tier case, the MEC serverco-located with each network access node in a given tier-l may beassumed to have the same computational capacity C_(l). If for a per-nodecase, the MEC server co-located with each network access node may have aunique computational capacity. This information about computationalcapacities may also be provided to input data memory 10702 from a corenetwork server or other location that stores information about thecapabilities of network access nodes in a given network.

After collecting these parameters in stage 10802, input data memory10702 may provide the parameters to bias processor 10704. Bias processor10704 may then compute the uplink bias values using stochastic geometrytools in stage 10804. As previously indicated, the bias value for agiven tier or given individual network access node may reflect thecapability of the given tier-l or individual network access node ofmeeting the data rate and latency demands of terminal device application9702. Bias processor 10704 may therefore use stochastic geometry toolsto probabilistically model the distribution of network access nodes andto model whether or not the network access nodes and their co-locatedMEC servers are able to meet the data rate and computational capacitydemands of terminal device application 9704. Bias processor 10704 maycompute higher uplink bias values for tiers and/or network access nodesthat are more likely, according to results obtained by stochasticgeometry-based performance analysis, of meeting the demands of terminaldevice application 9704. In some aspects, bias processor 10704 maydesign per-tier and/or per-QOS bias values for multi-tier networks,where different bias values are determined for different tiers and fordifferent QOS parameters of various applications. After computing theuplink bias values in stage 10804, bias processor 10704 may provide theuplink bias values to cell association controller 9800, which mayexecute the cell association function to select an uplink network accessnode for terminal device 9702 using the uplink bias values B_(l).

Two examples related to computation of uplink bias values by biasprocessor 10704 will now be described with reference to FIGS. 101 and102 . These examples related to a per-tier case where there is a tier-Mof macro network access nodes and a tier-F of micro network accessnodes. In the first example using FIG. 101 , terminal device application9704 may have a small amount of uplink data d_(UE) to send forprocessing by peer application 9722 but may have a large computationalcapacity demand c_(UE) (e.g., a demanding computational task for peerapplication 9722). As there is only a small amount of uplink data d_(UE)for uplink transmission, terminal device 9702 may only have moderateuplink SINR demands γ_(UL,th). Accordingly, focusing on the task latencydemand t_(delay,th), this SINR demand γ_(UL,th) will in principleincrease t_(delay) ^(trans) (per Equation (1)) due to thecorrespondingly low uplink data rate. However, for small amounts of datad_(UE), the transmission delay can be considered negligible, and themain part of the delay will be the execution delay t_(delay) ^(exe).Bias processor 10704 may therefore compute the bias valuesB_(UL)(γ_(UL,th),t_(delay,th)), k={M,F} so that cell associationcontroller 9800 (when executing the cell association function) biasesthe selection towards macro network access nodes. In some cases, thiscan be important when the deployment density λ_(F) of macro networkaccess nodes is comparable to the deployment density λ_(M) of macronetwork access nodes and/or the computational capacity C_(M) of macroMEC servers is much larger than the computational capacity C_(F) ofmicro MEC servers (e.g., C_(M)>>C_(F)).

In the second example using FIG. 102 , terminal device application 9704may have a considerable amount of uplink data d_(UE) to send forprocessing by peer application 9722, and may have light computationalcapacity demand c_(UE) (e.g., a small computational task). Accordingly,while the processing demand c_(UE) takes a moderate to small value,terminal device 9702 may have a more demanding uplink data rate/SINRdemand y_(UL,th) to control t_(delay) ^(trans). Accordingly, biasprocessor 10704 may design bias values B_(k)(γ_(UL,th),t_(delay,th)),k={M,F} so that the cell association controller 9800 is biased towardsselecting a closest micro network access node (e.g., micro networkaccess node 9720 given the exemplary location of terminal device 9702 inFIG. 102 ) when it executes the cell association function. Accordingly,even though macro network access nodes may be co-located with macro MECservers with larger computational capacity C_(M) than the micro MECservers co-located with micro network access nodes, the considerabledata rate demands γ_(UL,th) of terminal device application 9704 may meanthat a closest micro network access node may be a more suitable choice.Design of bias values B_(l) by bias processor 10704 that bias towardselecting a closest micro network access nodes may therefore beadvantageous in this example.

In some aspects, bias processor 10704 may also consider energyconsumption of terminal device 9702, such as where Single-InputSingle-Output (SISO) communication is used with the aim of achieving thedata rate/SINR demand γ_(UL,th) in an energy efficient manner. Biasprocessor 10704 may therefore also compute the bias values B_(l) so thatthe cell association function is shaped towards minimizing energyconsumption of terminal device 9702.

FIG. 109 shows exemplary method 10900 of controlling cell associationaccording to some aspects. As shown in FIG. 109 , method 10900 includesdetermining biased received powers for a plurality of network accessnodes based on respective bias values for the plurality of networkaccess nodes (10902), identifying a maximum biased received power fromthe biased received powers and identifying a corresponding networkaccess node of the plurality of network access nodes having the maximumbiased received power (10906), and selecting the network access node asa target network access node for the terminal device to associate with(10908).

FIG. 110 shows exemplary method 11000 of controlling cell associationaccording to some aspects. As shown in FIG. 110 , method 11000 includesdetermining biased uplink received powers fora plurality of networkaccess nodes based on respective uplink bias values for the plurality ofnetwork access nodes (11002), determining biased downlink receivedpowers for the plurality of network access nodes based on respectivedownlink bias values for the plurality of network access nodes (11004),evaluating the biased uplink received powers and the biased downlinkreceived powers to identify a maximum biased uplink received power and amaximum biased downlink received power (11006), and selecting an uplinknetwork access node and a downlink network access node for the terminaldevice to associate with based on the maximum biased uplink receivedpower and the maximum biased downlink received power (11008).

FIG. 111 shows exemplary method 11100 of determining bias valuesaccording to some aspects. As shown in FIG. 111 , method 11100 includesobtaining first parameters related to data rate and latency demands of aterminal device application and obtaining second parameters related todata rate and computational capacity capabilities of a plurality ofnetwork access nodes (11102), and determining bias values for theplurality of network access nodes based on an evaluation of the firstparameters and the second parameters, wherein the bias values are basedon a capability of the plurality of network access nodes to support theterminal device application (11104).

Improved Access Control for Communication Systems

Communication systems, such as Carrier-Sense Multiple Access (CSMA)based systems, where communication devices may communicate via a sharedchannel without centralized access control, may rely on Listen BeforeTalk (LBT) protocols to control communication via the shared channel. Insuch systems, a communication device intending to transmit data via theshared channel may first have to listen to the shared channel todetermine if data transmission from different communication devices isongoing and the shared channel is occupied. In other words, when adifferent communication device uses the channel for data transmission,the communication device may not be able to transmit data itself. Insuch situations, the communication device may have to again listen tothe channel e.g. after a predefined time. The communication device maythen transmit its data, when the channel is not occupied by a datatransmission from a different communication device.

In such communication systems, in particular when a large number ofcommunication devices may intend to use a single shared channel at equaltimes, situations may occur where essentially all communication devicesmay have to wait for the shared channel to become free for their owndata transmission. In other words, in particular in situations whenmultiple communication devices may intend to use a shared channel fordata communication, LBT protocols may not be optimal for controllingaccess to a shared channel by said multiple communication devices. Suchsituations may be non-optimal, in particular when users intending totransmit data of higher priority, e.g. in an extreme case data for anemergency call, may have to wait an undesirably long time before theirdata can be transmitted.

In view of this, various aspects of the present disclosure provide acommunication device configured to generate and transmit (or broadcast)an own scheduling message and configured to receive a scheduling messagefor at least one further communication device. In accordance withvarious aspects, the communication device is further configured toprocess the generated and the received scheduling messages to determineat least one scheduling parameter for a transmission of data. Thus, invarious aspects, by processing scheduling messages for the communicationdevice and e.g. for multiple other communication devices, schedulingparameters for each communication device may be determined at eachcommunication device and an overall scheduling may be determined for agroup of communication devices. Such overall scheduling may in certainaspects be determined in accordance with priority information includedin each scheduling message. In this way, it may in various aspectsbecome possible to ensure early communication of high priority data,such as e.g. data for an emergency call.

FIG. 112 shows exemplary radio communication network 11200 according tosome aspects, which may include terminal devices 11201 to 11203 andnetwork access node 11206. As shown in FIG. 112 , the communicationsystem 11200 includes a terminal device MT1 11201, a terminal device MT211202, and a terminal device MT3 11203, distributed in an area 11205.The number of terminal devices is used only for illustrative purposesand is not limited to the example number of three. The terminal devices11201 to 11203 may be configured as described above for terminal device102 and examples of terminal devices 11201 to 11203 may include inparticular mobile terminals such as cellular phones, tablets, computers,vehicular communication devices, and the like. The communication system11200 further includes an access node 11206, which may for example be aWLAN or WiFi access point (AP) configured for example in accordance withan IEEE 802.11 standard. Exemplarily, the communication network 11200may employ a carrier-sense multiple access (CSMA) scheme for managingcommunication between the terminal devices 11201 to 11203 while achannel for communication of data between terminal devices 11201 to11203 may be usable for data transmission of a single one of theterminal devices 11201 to 11203 at a time.

FIG. 113 shows an exemplary method 11300 according to which terminaldevices 11201 to 11203 may communicate following a CSMA scheme. Asillustrated, in stage 11302, terminal device 11201 (describedexemplarily for terminal devices 11201 to 11203) prepares user data fortransmission, e.g. processes data in accordance with formattingprotocols related to the physical layer. Thereafter, in stage 11305,terminal device 11201 listens to a channel which may be establishedbetween the terminal device 11201 and terminal devices 11202, 11203 viaaccess node 11206, and which the terminal devices 11201, 11202, 11203may share for communication of data between the terminal devices 11201,11202, 11203. In other words, in stage 11305, terminal device 11201 isconfigured to sense if data transmission between any other terminaldevices is ongoing via the channel. Such channel may e.g. be a dedicatedfrequency or frequency range and may e.g. correspond to a subrange of aglobal frequency range of a communication system. By listening to thechannel in this way, terminal device 11201 determines if the sharedchannel is occupied or free to be used. In the shown example, the sharedchannel is occupied when one of the terminal devices 11202 or 11203 usesthe channel for data transmission such that terminal device 11201 cannottransmit data itself during the time the data transmission is ongoing.

If the channel is occupied by a data transmission from a differentterminal device, the terminal device 11201 may wait for a period of timeΔt, e.g. a random Back-Off Time, in stage 11306 before listening againto the shared channel (stage 11305). If the channel is free to be used,the terminal device 11201 may transmit in stage 11309 the data preparedin stage 11302 after optionally having transmitted a Request to Send(RTS) message to the access node 11206 and having optionally received aClear to Send message (CTS) from the access node 11206. Such RTS messageand such CTS messages are examples for control information that may beexchanged between the terminal devices 11201 to 11203 and access node11206. The above CSMA scheme may in aspects be referred to as listenbefore talk (LBT) scheme.

In accordance with various aspects of the present disclosure,communication devices such as for example terminal devices as discussedabove are configured to generate a scheduling message, e.g. a PacketRequest Header (PRH), and are configured to receive a schedulingmessage, e.g. a PRH, for at least one further communication device. Inaspects, the scheduling message (which may in certain aspects be aseparate message or a header or preamble of a message including furtherdata) for the at least one further communication device is received bythe communication device from the at least one further communicationdevice. In various aspects, the communication device is configured toprocess the generated scheduling message and the received schedulingmessage to determine at least one scheduling parameter for atransmission of data and is configured to transmit the data inaccordance with the determined at least one scheduling parameter. Thescheduling messages may thus allow an efficient scheduling ensuring thateven in the case of multiple communication devices potentially trying toaccess a common shared channel or resource, each communication devicemay be assigned for example a communication resource (e.g. a frequencyor frequency range) for data transmission within a time interval.

In various aspects, the scheduling parameter defines a time interval ortransmission time interval during which the communication device maytransmit the data. To this end, the scheduling parameter may for exampledefine a start time and a length of such time interval. The schedulingparameter may alternatively or in addition define a frequency resource,e.g. a single frequency or a frequency range, for transmission of thedata.

In various aspects, the scheduling message may comprise first priorityinformation, e.g. a global priority information or a primary priorityinformation. In aspects, first priority information may include or be avalue representing the first priority information. In these aspects, thecommunication device may be configured to determine the schedulingparameter based on a comparison of first priority information of thegenerated scheduling message with first priority information of thereceived scheduling message. The first priority information may bedetermined by the communication device for a type of data to betransmitted. Alternatively or in addition, the first priorityinformation may be predefined for a type of data to be transmitted, e.g.by a standard and/or in a lookup table stored at the communicationdevice or at a different network node such as at an access node withwhich the communication device may communicate. For example, a type ofdata may define the data to be data for an emergency call or normalvoice communication. In this case, a first priority of data for anemergency call may be higher than a first priority for normal voicecommunication. A first priority may generally correspond to a firstpriority value and a first priority value of data for an emergency callmay have a higher value as a corresponding value for voicecommunication. Further types of data transmission to which respectivefirst priorities may be assigned may include (but are not limited to)conversational voice, conversational video, non-conversational video,vehicle-to-everything (V2X) messages, vehicle-to-vehicle (V2V) messages,or further different messages. Assignment of respective firstpriorities/first priority values to these types of communication may bepredefined by a standard and/or stored in a corresponding table in eachcommunication device.

In various aspects, the communication device may be configured totransmit the generated scheduling message to the at least one furthercommunication device within a scheduling time interval during which thecommunication device is configured to receive the scheduling message.Thereby, according to various aspects, a transmission time during whichthe communication device is configured to transmit the generatedscheduling message at least partially or fully overlaps with a receptiontime during which the communication device is configured to receive thescheduling message. In other words, the communication device and the atleast one further communication device may for example be configured tocommunicate scheduling messages essentially simultaneously, i.e. withinsaid scheduling time interval, e.g. using a full duplex scheme. Invarious aspects, the communication device is configured to transmit thegenerated scheduling message to the at least one further communicationdevice using at least one communication frequency and wherein the firstreceiver is configured to receive the scheduling message using the sameat least one communication frequency. In the case that schedulingmessages, e.g. PRHs, at least partially overlap in time and overlap infrequency can in various aspects be that scheduling messages mayautomatically collide and interfere at each communication device thusenabling reconstruction of each scheduling message at each communicationdevice in an efficient way, e.g. using interference cancellationprocessing schemes. In various aspects, the communication device may beconfigured to operate in a full duplex operation mode at least duringthe scheduling time interval.

In various aspects, the communication devices may for example form asystem of distributed communication devices where an assignment ofcommunication resources, e.g. time intervals and/or frequencies fortransmission of data is performed by exchanging scheduling messagesbetween the communication devices and by locally processing owngenerated and different received scheduling messages at eachcommunication device. In these aspects, each communication device maye.g. broadcast a scheduling message, e.g. a Packet Request Header (PRH),and may receive a scheduling message, e.g. a PRH, from at least onefurther communication device essentially at the same time, i.e. within ascheduling time interval preceding e.g. respective time intervals fordata transmission assigned to each communication device.

In various aspects, a scheduling message may further comprise secondpriority information. In these aspects, the communication device may beconfigured to determine the scheduling parameter based on a comparisonof second priority information of the generated scheduling message withsecond priority information of the received scheduling message when thefirst priority information of the generated scheduling message coincideswith or matches the first priority information of the receivedscheduling message.

For example, if in these aspects the communication device and the atleast one further communication device intend to communicate data of asame type, e.g. both communication devices intend to communicate datafor voice communication, the first priority information, e.g. the firstpriority value, of the generated scheduling message may match, i.e. beequal to, the first priority information, e.g. the first priority value,of the received scheduling message. A scheduling message may in theseaspects further comprise said second priority information, and thecommunication device may be configured to determine the schedulingparameter based on a comparison of second priority information of thegenerated scheduling message with second priority information of thereceived scheduling message. An effect of the second priorityinformation may be that a conflict can be avoided if first priorityinformation of respective scheduling messages is equal. In alternativeaspects, such conflict may be resolved differently, e.g. by assigningdifferent frequency resources to respective communication devices withina common transmission time interval.

The second priority information may be an offset value, or a randomvariable or a number. Such value, variable or number may for example bechosen from a range 0 to 1023, for example from a range 0 to 2047, forexample from a range 0 to 4094, for example from a range 0 to 8191, forexample from a range 0 to 16383, for example from a range 0 to 32767, orgenerally from a range 0 to 2^(N)−1, N being chosen in accordance e.g.with the size of a group of communication devices and e.g. predefined ina standard, N being e.g. an empirical value. In other words, theseranges or different ranges may be chosen or predefined for example inaccordance with a number of communication devices typically forming arespective distributed system of communication devices. In aspects arange may for example be dynamically set by and for each communicationdevice in accordance with a current number of communication devicesand/or may be defined by a standard and/or may be stored in a dedicatedmemory of a communication device. In various aspects, the secondpriority information may be generated by the communication device forthe generated scheduling message or may be selected by the communicationdevice for the generated scheduling message from a table stored at thecommunication device. For example, a random number may used as secondpriority value or a number may be chosen based on a user ID, a terminalID, or the like. In addition or alternatively, the second priorityparameter may be set semi-statically in accordance with details inrelation to the communication device. For example, a communicationdevice roaming in a network of a different contractor may be assigned afixed lower value of said priority parameter or offset value during thetime it is roaming in the network of the different contractor. Duringthis time, the communication device may also be assigned a restrictedrange of the random number, e.g. from 0 to 2047 (i.e. 0 to (2^(N)−1)/2)as opposed to a range of e.g. 0 to 4095 (i.e. 0 to (2^(N)−1)) assignedto a communication device being in a network of its own contractor. Invarious aspects, in addition or alternatively, the second priorityinformation may be communicated between the communication device and theat least one further communication device using further schedulingmessages after processing of first scheduling messages communicatedbetween the communication device and the at least one furthercommunication device yielded matching first priority information of thefirst scheduling messages.

FIG. 114 shows exemplary radio communication network 11400 according tovarious aspects of the present disclosure, which may includecommunication devices 11401 to 11403. As shown in FIG. 114 , thecommunication system 11400 includes a communication device MT1 11401, acommunication device MT2 11402, and a communication device MT3 11403,distributed in an area 11405. Area 11405 may for example be ageographical area determined by combined geographicaltransmission/reception ranges of communication devices 11401 to 11403.The number of communication devices is used only for illustrativepurposes and is not limited to the example number of three. Thecommunication devices 11401 to 11403 may be configured as describedabove for communication device 102 and examples of communication devices11401 to 11403 may include in particular mobile terminals such ascellular phones, tablets, computers, vehicular communication devices,and the like. As shown in FIG. 114 , the communication devices 11401 to11403 may in various aspects be configured to communicate with asatellite 11410, e.g. included in a global navigation satellite system(GNSS). Global navigation satellite systems include exemplarily (but arenot limited to) the Global Positioning System (GPS), GLONASS, Galileo,the BeiDou Navigation Satellite System, the BeiDou-2 GNSS.

In various aspects, the communication device is configured to receive aclock signal defining the scheduling time interval. For example, theclock signal may be configured to define a start time of the schedulingtime interval. In various aspects, the communication device isconfigured to receive the clock signal from satellite 11410 illustratedin FIG. 114 . In FIG. 114 , arrows between GNSS satellite 11410 and eachcommunication device 11401 to 11403 exemplarily illustrate transmissionof the clock signal. Arrows between respective ones of the communicationdevices 11401 to 11403 exemplarily illustrate transmission of schedulingmessages and subsequent transmission of data between the communicationdevices 11401 to 11403.

FIG. 115 shows exemplary radio communication network 11500 according tovarious aspects of the present disclosure, which may includecommunication devices 11501 to 11503. As shown in FIG. 115 , thecommunication system 11500 includes a communication device MT1 11501, acommunication device MT2 11502, and a communication device MT3 11503,distributed in an area 11505. The number of communication devices isused only for illustrative purposes and is not limited to the examplenumber of three. The communication devices 11501 to 11503 may beconfigured as described above for communication device 11502 andexamples of communication devices 11501 to 11503 may include inparticular mobile terminals such as cellular phones, tablets, computers,vehicular communication devices, and the like. As shown in FIG. 115 ,alternatively or in addition to the case shown in FIG. 114 , in variousaspects the communication devices 11501 to 11503 may be configured tocommunicate with a base station 11511 of a communication network whichmay be an access node 110 as disclosed in the context of FIG. 3 . Area11505 may for example be a geographical area determined by combinedgeographical transmission/reception ranges of communication devices11501 to 11503 or may be a geographical area covered by base station11511.

In various aspects, the communication device is configured to receivethe clock signal from a base station of a communication network such ase.g. base station 11511, the clock signal defining the scheduling timeinterval. In FIG. 115 , arrows between base station 11511 and eachcommunication device 11501 to 11503 exemplarily illustrate transmissionof the clock signal. Arrows between respective ones of the communicationdevices 11501 to 11503 exemplarily illustrate transmission of schedulingmessages and subsequent transmission of data between the communicationdevices 11501 to 11503.

In various aspects, the base station 11511 may provide said clock signalto communication devices 11501 to 11503, while scheduling messages andsubsequent data traffic is exchanged between the communication devices11501 to 11503 directly (as illustrated in FIG. 115 ). Alternatively orin addition, in certain aspects, the scheduling messages and/or saiddata traffic can be relayed via base station 11511 to be exchangedbetween communication devices 11501 to 11503. In various aspects,communication device 11501 may further access a network such as theInternet and/or mobile communication networks via base station 11511 andmay communicate scheduling messages and subsequent data with thecommunication devices 11502 to 11503 directly (or relayed by the basestation 11511).

In various aspects, the base station 11511 may further provide controlinformation to the communication devices 11501 to 11503 while assignmente.g. of transmission time intervals for data transmission and/orcommunication resources for data transmission is performed among thecommunication devices 11501 to 11503 by exchange of scheduling messages.In aspects, control information provided by the base station 1011 mayinclude control messages such as RTS and CTS messages. In aspects, suchcontrol information from base station 11511 may include controlinformation to assist decoding of scheduling messages at eachcommunication device 11501 to 11503. For example, in these aspects, suchcontrol information may include information regarding a number ofterminals e.g. present in area 11505. For example, in these aspects,such control information may include information regarding resourceallocation of the scheduling messages, e.g. information on whichfrequency or within which frequency range the scheduling messages arebroadcasted by each communication device.

FIG. 116 shows exemplary radio communication network 11600 according tovarious aspects of the present disclosure, which may includecommunication devices 11601 to 11603 and master communication device11612. As shown in FIG. 116 , the communication system 11600 includes acommunication device MT1 11601, a communication device MT2 11602, acommunication device MT3 11603, and a master communication device MMT11612, distributed in an area 11605. The master communication device11612 may correspond to communication devices 11601 to 11603. Thecommunication devices 11601 to 11603 and master communication device11612 may be configured as described above for communication device 102and examples of communication devices 11601 to 11603 and for mastercommunication device 11612 may include in particular mobile terminalssuch as cellular phones, tablets, computers, vehicular communicationdevices, and the like. Area 11605 may for example be a geographical areadetermined by combined geographical transmission/reception ranges ofcommunication devices 11601 to 11603 and 11612. The number ofcommunication devices is used only for illustrative purposes and is notlimited to the example number of four.

As shown in FIG. 116 , the communication devices 11601 to 11603 may invarious aspects be configured to communicate with master communicationdevice 11612, which in these aspects may take the functions of satellite11410 and/or of base station 11511. In various aspects, thecommunication device is configured to receive the clock signal from atleast one communication device, i.e. from the master communicationdevice 11612, the clock signal defining the scheduling time interval. Inthese aspects, master communication device 11612 is configured totransmit said clock signal to communication devices 11601 to 11603. InFIG. 116 , arrows between master communication device 11612 and eachcommunication device 11601 to 11603 exemplarily illustrate transmissionof the clock signal. Arrows between respective ones of the communicationdevices 11601 to 11603 and master communication device 11612 exemplarilyillustrate transmission of scheduling messages and subsequenttransmission of data between the communication devices 11601 to 11603.In addition to clock signals, the master communication device 11612 maybe configured to transmit control information to communication devices11601 to 11603 corresponding to the control information described abovein the context of base station 11511.

In various aspects, communication devices may be configured inaccordance with communication devices 11601 to 11603 and/or inaccordance with communication devices 11501 to 11503 and/or inaccordance with communication devices 11401 to 11403 and may communicatewith satellite 11410, base station 11511, and/or master communicationdevice 11612 for example depending on availability of satellite 11410and/or base station 11511 and/or master communication device 11612and/or for example depending on signal strength of signals received fromsatellite 11410 and/or base station 11511 and/or master communicationdevice 11612.

For example, if both satellite 11410 and base station 11511 areavailable, the communication device may be configured to prioritizecommunication with the base station 11511 (reception of clock signaland/or reception of the above described control information) overcommunication with the satellite 11410 (reception of clock signal), orvice versa. Depending on availability, the communication device may alsoswitch from communication with the satellite 11410 to communication withthe base station 11511. For example, the communication device may switchfrom communication with one of satellite 11410 or base station 11511 tocommunication with the other one of satellite 11410 or base station11511 depending on signal strength of a received signal, e.g. a receivedclock signal. Further, for example, if neither base station 11511 notsatellite 11410 is available for communication or signal strength ofrespectively received signals is below a predefined threshold, thecommunication device may switch to reception of clock signals frommaster communication device 11612.

In various aspects, a communication device may be configured to takefunctions of master communication device 11612 based on correspondingcontrol information received from a node such as base station 11511. Forexample, base station 11511 may transmit a corresponding control signalto one communication device selected from a group of communicationdevices, when communication quality for the group of communicationdevices with the base station 11511 degrades, e.g. when signal strengthof clock signals received by the group of communication devices fallsbelow a threshold. Such situation may for example occur in the case thata group of communication devices (e.g. vehicular communication devices)moves away from the base station 11511. Degradation of communicationquality may be determined at the base station 11511 based on measurementreports received from at least one communication device and/or at atleast one communication device, e.g. based on a receivedsignal-to-interference-plus-noise ratio (SINR).

In alternative aspects, a communication device may be configured to takethe functions of master communication device 11612 following acorresponding message exchange within a group of communication devices.For example, corresponding messages may be triggered within a radiodiscovery procedure when communication devices within a group ofcommunication devices are in proximity (e.g. within area 11605), andeach communication device can be discovered by other communicationdevices within said group. A communication device within said group maybe configured to take the functions of master communication device 11612for example based on capability to transmit clock signals to othercommunication devices. Alternatively or in addition, further priorityinformation corresponding e.g. to the second priority information may beexchanged to determine a communication device to take the functions ofmaster communication device 11612 within said group of communicationdevices.

FIG. 117 shows an exemplary internal configuration of a communicationdevice 11401 in accordance with various aspects of the presentdisclosure. Communication devices 11402, 11403, 11501, 11502, 11503,11601, 11502, 11603 and 11612 may be configured in an equal or similarmanner. The communication device 11401 of FIG. 117 may correspond to theterminal device 102 shown in FIG. 2 . As the illustrated depiction ofFIG. 117 is focused on aspects in relation to transmission, receptionand processing of scheduling messages, for purposes of conciseness, FIG.117 may not expressly show certain other components of terminal device102. As shown in FIG. 117 , in some aspects, the communication device11401 may include a digital signal processing subsystem 11701, ascheduling message (SM) generator 11702, a scheduling message (SM)transmitter 11704, a scheduling message (SM) receiver 11705, ascheduling message (SM) processor 11706, a scheduler 11708, a datatransmitter 11709, a clock signal receiver 11703 and a timer 11707. Eachof digital signal processing subsystem 11701, scheduling messagegenerator 11702, scheduling message transmitter 11704, schedulingmessage receiver 11705, scheduling message processor 11706, scheduler11708, data transmitter 11709, clock signal receiver 11703 and timer11707 may be incorporated in or may for example be part of the basebandmodem 206 of the terminal device 102 shown in FIG. 2 . Each of digitalsignal processing subsystem 11701, scheduling message generator 11702,scheduling message transmitter 11704, scheduling message receiver 11705,scheduling message processor 11706, scheduler 11708, data transmitter11709, clock signal receiver 11703 and timer 11707 may be structurallyrealized as hardware (e.g., as one or more digitally-configured hardwarecircuits, such as ASICs, FPGAs, or another type of dedicated hardwarecircuit), as software (e.g., one or more processors configured toretrieve and execute program code that defines arithmetic, control,and/or I/O instructions and is stored in a non-transitorycomputer-readable storage medium), or as a mixed combination of hardwareand software. While digital signal processing subsystem 11701,scheduling message generator 11702, scheduling message transmitter11704, scheduling message receiver 11705, scheduling message processor11706, scheduler 11708, data transmitter 11709, clock signal receiver11703 and timer 11707 are shown separately in FIG. 117 , this depictiongenerally serves to highlight the operation of the communication device11401 on a functional level. Digital signal processing subsystem 11701,scheduling message generator 11702, scheduling message transmitter11704, scheduling message receiver 11705, scheduling message processor11706, scheduler 11708, data transmitter 11709, clock signal receiver11703 and timer 11707 can therefore each be implemented as separatehardware and/or software components, or one or more of digital signalprocessing subsystem 11701, scheduling message generator 11702,scheduling message transmitter 11704, scheduling message receiver 11705,scheduling message processor 11706, scheduler 11708, data transmitter11709, clock signal receiver 11703 and timer 11707 can be combined intoa unified hardware and/or software component (for example, ahardware-defined circuitry arrangement including circuitry to performmultiple functions, or a processor configured to execute program codethat defines instructions for multiple functions).

FIG. 118 shows exemplary method 11800, which communication device 11401may execute using the internal configuration shown in FIG. 117 . Thecommunication device 11401 may prepare information bits of data fortransmission in a next transmission time interval (a transmission timeinterval following an exchange and a processing of scheduling messages)in stage 11802 using the digital signal processing subsystem 11701. Datapreparation may in certain aspects involve procedures followingformatting protocols related to the physical (PHY) layer such as dataprotection using forward error correction (FEC), mapping of encoded datato predefined modulation symbols, e.g. QPSK or QAM modulation symbols,or the like. In certain aspects, a communication device may in anoptional stage 11804 switch a transmission mode from a half duplex (HD)mode to a full duplex (FD) mode so that each communication device 11401may transmit data and may essentially at the same time (e.g. within acommon time interval) receive data. Stage 11804 (and stage 11814) may beoptional e.g. if a communication device does not need to switch to afull duplex mode.

In stage 11806, a clock signal received via clock signal receiver 11703may initiate a resource negotiation stage 11808 between thecommunication devices 11401, 11402, 11403, which may correspond to ascheduling time interval. As described, the clock signal can be a signalfrom a global navigation satellite system (GNSS) 11410. During theresource negotiation stage or scheduling interval 11808, eachcommunication device 11401 may broadcast a scheduling message (generatedscheduling message) generated with scheduling message generator 11702via scheduling message transmitter 11704 while it may receive schedulingmessages (received scheduling messages) from each other communicationdevice 11402, 11403 using scheduling message receiver 11704.

In certain aspects, the communication device may be configured totransmit the generated scheduling message to the at least one furthercommunication device using at least one communication frequency and thecommunication device may be configured to receive the scheduling messageusing the same at least one communication frequency. For example, allcommunication devices 11401, 11402, 11403 may communicate all schedulingmessages within a scheduling time interval using a common frequencyrange. Using the common frequency range, the scheduling messages maycollide and interfere. In various aspects, the communication device maybe configured to perform interference cancellation processing toreconstruct the received scheduling message from a received signal. Forexample, a received signal may be a combined signal comprising thegenerated scheduling message from the communication device itself (e.g.as a self-transmitted scheduling message) and the received schedulingmessage from a different communication device. The self-transmittedscheduling message may be a scheduling message transmitted by thecommunication device and received by a receiver of the communicationdevice itself at the same time. The received signal may be a combinedsignal comprising a plurality of scheduling messages from thecommunication device and from a plurality of respective differentcommunication devices. Using interference cancellation processing, thecommunication device may reconstruct each of the scheduling messagesreceived from each respective one of the different communicationdevices. In various aspects, the communication device may be configuredto perform successive interference cancellation to first cancelself-transmitted scheduling messages (e.g. PRHs) and then decode andcancel the second strongest received scheduling message (e.g. PRH), andany subsequent scheduling messages e.g. ordered by a respective signalstrength. In various aspects, successive interference cancellation maybe performed until a stop criterion is reached, e.g. when a maximumnumber of iterations is reached or when a quality measurement (e.g. acyclic redundancy check) is below a predefined threshold).

In various aspects, a transmission format of each scheduling message maybe predefined, and upon processing the generated scheduling message andthe received scheduling message, the communication device may beconfigured to reconstruct the received scheduling message from areceived signal based on a respective predefined format of the receivedscheduling message. For example, such predefined format of thescheduling messages may be predefined by a standard and/or may be storedin a corresponding memory of the communication device. Such predefinedformat of the scheduling message (which may in certain aspects be aseparate message or a header or preamble of a message including furtherdata) may facilitate reconstruction of scheduling messages viainterference cancellation.

In certain aspects, for example the scheduling message receiver 11704 ofeach communication device 11401 may apply in particular successiveinterference cancellation and may thus decode and subtract a strongerscheduling message out of a combined received signal including allscheduling messages from the combined signal to extract a weakerscheduling message from the combined data signal. Further, in certainaspects, using e.g. knowledge of said predefined scheduling messageformats, the scheduling message receiver 11704 of each communicationdevice 11401 may attempt to decode all scheduling messages in paralleland may determine if decoding of a scheduling message has beensuccessful or not using e.g. CRC. The communication device 11401 maythen apply dedicated interference cancellation using the schedulingmessages that have passed the CRC to recover those scheduling messagesthat have not passed the CRC. In various aspects, channel codingredundancy is applied to each scheduling message for protection. Incertain aspects, a higher degree of redundancy may be applied toscheduling message including a higher first priority. For example, ascheduling message for a communication device that intends to transmitdata of an emergency message or call may include a highest firstpriority and may be provided with a corresponding highest degree ofredundancy.

In certain aspects, communication devices may broadcast schedulingmessages in predefined or dynamically chosen subranges of a globalfrequency range. In these aspects, collisions of scheduling messages arerestricted to the respective subranges and corresponding communicationdevices may apply interference cancellation processing within thesesubranges to reconstruct respective scheduling messages. The subrangemay e.g. be predefined by a standard and stored for each communicationdevice in a corresponding memory.

Subsequent to the resource negotiation stage 11808, a scheduling messageprocessor 11706 of each communication device 11401 may locally processthe received scheduling messages and its own (the generated) schedulingmessage in stage 11810 by applying a dedicated algorithm. The algorithmcan in certain aspects be predefined by a standard and can be stored ina local memory of each communication device 11401. By applying thededicated algorithm, the scheduling message processor 11706 maydetermine a scheduling parameter. In certain aspects, the schedulingparameter may define a transmission time interval and the communicationdevice may be configured to transmit the data during the transmissiontime interval. In certain aspects, in addition or alternatively, thescheduling parameter may define a frequency resource and thecommunication device may be configured to transmit the data using thefrequency resource.

In certain aspects, the scheduling message processor 11706 may thusdetermine resource assignment for the communication device 11401 to beused in a transmission interval following the resource negotiation stage11808. Based on the scheduling parameter, e.g. the assigned frequencyresources and the assigned time interval, a scheduler 11708 may scheduletransmission of data in said transmission time interval for thecommunication device 11401. Data transmission may thus be performed in ashared channel, e.g. a predefined frequency band by one communicationdevice only within an assigned transmission time interval, or more thanone communication device may transmit data within said transmission timeinterval using respectively assigned frequency resources. The schedulingparameter may include a start time and a length of the time interval foreach communication device or the length may be a predefined value fixedby a standard and may be stored e.g. in a local memory of eachcommunication device 11401.

In various aspects, scheduling messages of each communication device11401, 11402, 11403 may be transmitted in a predefined subrange of aglobal frequency range. The subrange may e.g. be predefined by astandard and may be stored for each communication device 11401, 11402,11403 in a corresponding memory. In certain aspects, the schedulingmessages communicated within the subrange of the frequency range caninclude control information to assign the same or different frequencyranges within the global frequency range, including the entire globalfrequency range, to communication devices for data transmission in anassigned time interval. In certain aspects, a subrange of a globalfrequency range within which a scheduling message may be broadcasted bya communication device may be dynamically chosen for the communicationdevice for each resource negotiation stage.

Referring back to FIGS. 117 and 118 , having processed the own(generated) and the received scheduling messages in stage 11810, thescheduling message processor 11706 may in certain aspects pass thedetermined scheduling parameter to the scheduler 11708 which determinesif the own communication device 11401 is scheduled for data transmissionat stage 11812. The scheduler 11708 may for example refer to a timer11707 started in synchrony with a received clock signal, e.g. atreception of the clock signal or at another suitable point in time, e.g.when the scheduling parameter is passed from the scheduling messageprocessor 11706 to the scheduler 11708. The timer 11707 may be startedat the point in time, e.g. when the scheduling parameter is passed fromthe scheduling message processor 11706 to the scheduler 11708 for aduration indicating a start of a time interval assigned to communicationdevice 11401 for data transmission. In certain aspects, a timer being insynchrony with a clock signal may ensure that all communication devices11401, 11402, 11403 refer to a common time.

In certain aspects, if the scheduler 11708 determines that the time e.g.indicated by the timer (e.g. upon expiry of said timer) corresponds to astart of an assigned transmission time interval, a mode of communicationdevice 11401 may be switched from a full duplex mode to a half duplexmode at stage 11814. Subsequently, communication device 11401 maytransmit data at stage 11816 using data transmitter 11709 during thetime interval assigned by the resource assignment. If the time does notyet equal start of the assigned time interval, the scheduler 11708 mayin aspects perform waiting processing at stage 11813, e.g. may starttimer 11707 again, or may wait until timer 11707 is expired.

FIGS. 119A and 119B show timing diagrams in accordance with certainaspects. As shown, e.g. initiated by a global clock signal, thecommunication devices 11401, 11402, 11403 may first perform resourcenegotiation in time interval t_(m) (resource negotiation stage 11808) infull duplex mode. During this resource negotiation tin, eachcommunication device may receive multiple scheduling messages fromdifferent communication devices while at the same time broadcasting anown (generated) scheduling message. Even though only one negotiationsession is exemplarily shown, in various aspects, further negotiationsmay be employed. For example, in a first negotiation session, schedulingmessages may be exchanged among a plurality of communication devices toarrive at an assignment of time intervals for data transmission for eachcommunication device. In a further negotiation session, schedulingmessages may be exchanged among communication devices to assignfrequency resources to each communication device. In addition oralternatively, for example, in a first resource negotiation session,first priorities may be compared and if necessary (if first prioritiesare found to be matching), second priorities may be compared in asubsequent resource negotiation session. A further negotiation session(in advance or subsequently) may determine a communication device totake the functions of master communication device 11612.

In aspects, after having run a dedicated algorithm locally over thegenerated and the received scheduling messages, each communicationdevice may perform processing for scheduling its own data transmissionin accordance with assigned resources during a switching gap t_(gap).During the switching gap t_(gap), communication devices may in certainaspects switch from a full duplex mode to a half duplex mode. Followingthe switching gap t_(gap), the communication devices may transmit datain accordance with the resource assignment in a data communicationsession, which may precede a further resource negotiation session.

In FIGS. 119A and 119B, data communication sessions are denoted ast₁₁₄₀₁, t₁₁₄₀₂ and t₁₁₄₀₃, respectively indicating data communicationsessions for communication devices 11401, 11402 and 11403. As shown inFIG. 119A, the scheduling parameter may define a time interval within aglobal frequency range (the y-axis in the figure indicates frequency,the x-axis indicates time) only to a the communication device 11401 fordata transmission. Following this time interval, a further communicationdevice may be assigned a further time interval for data transmission orthe time interval may be flowed by a new resource negotiation sessionamong all communication devices. In the latter case, in certain aspects,e.g. a first priority and/or the second priority for the communicationdevice that has already transmitted data (communication device 11401 inFIG. 119A) may be restricted.

Further, shown in FIG. 119B, the scheduling parameter may definerespective subranges of the global frequency range to respectivecommunication devices (communication devices 11401 and 11402 in 119B)within a common time interval (within this time interval, datatransmission times for each communication device may differ as indicatedby the respective lengths of t₁₁₄₀₁, t₁₁₄₀₂ along the x-axis).Subsequent to said interval, a time interval film during which a furthercommunication device (communication devices 11403 in 119B) is assignedthe global frequency range for data transmission. As illustrated, incertain aspects e.g. a first priority may be set such that datacommunication types requiring less bandwidth have a higher priority,which in certain aspects may have the effect that more communicationdevices may gain a quick access to a communication channel.

FIGS. 120A and 120B, illustrate frequency resources that may in certainaspects be used for broadcasting scheduling messages. According to anaspect illustrated in the FIG. 120A, an exemplary number of tencommunication devices within a group of distributed communicationdevices broadcasts respective scheduling messages SM1, SM2, . . . SM10using a common frequency range, the scheduling messages being separatede.g. by code division multiplexing (CDM). In this aspect, all schedulingmessages SM1, SM2, SM10 collide in the frequency domain and eachcommunication device may reconstruct each of the scheduling messagesreceived from the other communication devices e.g. applying interferencecancellation techniques such as successive interference cancellation.

In certain aspects as exemplarily illustrated in FIG. 120B, eachcommunication device may select a random subrange of a global frequencyrange to transmit a scheduling message. In certain aspects, eachcommunication device may apply a blind search to determine a range ofpossible frequency resources. For example, a communication device mayinitially not be aware of frequency locations of all schedulingmessages. The communication device may attempt to decode a number ofpossible frequency ranges until a decoding result passes e.g. a cyclicredundancy check (CRC). In this way, a communication device notinitially aware of frequency ranges used for broadcast of schedulingmessages may apply blind decoding to determine and decode existingscheduling messages. In such aspects, e.g. scheduling messages SM1 andSM3 shown in FIG. 120B do not collide so that interference is reduced.Therefore, in such aspects, less interference per subrange of the globalfrequency range may facilitate decoding of scheduling messages withinsaid subrange. A resource assignment for a subsequent data transmissioncan in these aspects be restricted to the respective subrange, i.e. acommunication device broadcasting SM1 in the shown subrange may alsotransmit the scheduled data using the same subrange. Alternatively,subranges for subsequent data transmission may be negotiated using thescheduling messages.

As discussed above, in various aspects of the present disclosure, ascheduling message may define a transmission time interval and/or afrequency range to be used for data transmission. In further aspects,the generated scheduling message may comprises information on atransmission power, a modulation scheme, and/or a coding rate fortransmission of the data by the communication device. Accordingly, inthese aspects the received scheduling message may comprise informationon a transmission power, a modulation scheme, and/or a coding rate for atransmission of data by the at least one further communication device.The processor is then configured to determine the scheduling parameterbased on a comparison of the information on the transmission power, themodulation scheme, and/or the coding rate of the generated schedulingmessage with the information on the transmission power, the modulationscheme, and/or the coding rate of the received scheduling message.

In other words, in various aspects, each scheduling message may includein addition or alternatively to a transmission time interval and/or afrequency resource transmission parameters such as transmission power,modulation scheme, coding rate, which a corresponding communicationdevice intends to apply in the subsequent data transmission. Further,each scheduling message may alternatively or in addition include astransmission parameter an indication of a number of transmission layers,i.e. data streams with dedicated codewords (data block with errorprotection) a communication device configured for Multiple InputMultiple Output (MIMO) communication intends to transmit concurrently inan assigned time interval.

Such transmission parameters may be employed by each communicationdevice e.g. for assisting interference cancellation and may also beemployed in determining the resource assignment. For example, thetransmission parameters may be used by the local algorithm used by eachcommunication device for processing of the scheduling messages to derivean optimal resource allocation for a subsequent data transmission. Forexample, in certain aspects multiple data transmissions may be performedin a time/frequency grid during the data communication session. In suchaspects, for example a number of resource blocks assigned to datatransmission of a communication device may be determined based on acoding rate the communication device intends to use for the datatransmission and therefore includes into the scheduling message. Infurther aspects, for example a communication device, which has asignificantly higher (or lower) transmission power than the othercommunication devices within a common area (e.g. area 11405) may beassigned no transmission time interval in order to avoid power imbalanceat the receiver side.

As described above, in various aspects, scheduling messages arebroadcasted essentially synchronously by a plurality of communicationdevices in a common scheduling time interval e.g. using a commonfrequency range. The scheduling messages thus colliding can bereconstructed at each communication device using dedicated interferencecancellation schemes.

In alternative aspects, transmission of scheduling messages amongcommunication devices within a plurality of communication devices may beunsynchronized within a common frequency range. In these aspects,scheduling messages may collide with ongoing data transmission. In theseaspects, scheduling message processor 11706 of a communication device11401 receiving a scheduling message from a different communicationdevice while transmitting data different from a scheduling message (datatransmission and scheduling message reception in a full duplex mode) mayapply dedicated whitening/filtering algorithms to decode the receivedscheduling message. In these aspects, scheduling messages may beprovided with a sufficient amount of redundant bits such that schedulingmessages can be reconstructed at the communication devices.

In these aspects, a scheduler 11708 of each communication device mayfurther take into account ongoing data traffic in a frequency rangewithin which a communication device intends to transmit data byemploying a CSMA listen before talk scheme as illustrated in FIG. 113 .In other words, in these unsynchronized aspects, a communication devicebeing scheduled to transmit data in a certain frequency range based on ascheduling message negotiation, may listen to the frequency range untilongoing data transmission is terminated before starting its own datatransmission.

FIG. 121 shows exemplary method 12100 for a communication deviceaccording to some aspects. As shown in FIG. 121 , method 12100 includesgenerating a scheduling message (12102), receiving a scheduling messagefor at least one further communication device (12104), processing thegenerated scheduling message and the received scheduling message todetermine at least one scheduling parameter for a transmission of data(12106), and transmitting the data in accordance with the determined atleast one scheduling parameter (12108).

Full-Duplex Small Cell Based with Extreme Fast Link Adaptation

Currently methods for LTE link adaptations are performed in a verycoarse manner because of the time duration between the channel stateestimation and the channel state feedback is too long due to the largepropagation delay, the UE reporting delay in frequency division duplex(FDD), and/or the Tx/Rx duplexing delay in time division duplex (TDD).

In some aspects, devices are configured to transmit uplink and downlinksignals (e.g., reference signals) on the same time-frequency resourcesfor preserving channel reciprocity and avoiding processing delays inorder to perform a more robust and efficient link adaptation within achannel coherence time. Terminal devices and/or network access nodes maybe configured to immediately perform channel estimation and beginpre-equalization as soon as reference signals are received since each ofthe respective communication devices will be able to use its owntransmitted reference signal as a self-interferer in interferencecancellation. Accordingly, a number of benefits may be realized, such asimproved and/or faster link adaptation, pre-code selection, and sub-bandselection.

Network access nodes, especially those deployed as small cell basestations, may make use of the full duplexing for link adaptation betweenthe respective network access node and connected terminal devices. Thisfull duplex mode (FD) mode (including a partial FD mode, wherein onlypilots/reference symbols are duplexed) may be implemented from theterminal device to the network access node, and/or vice versa, dependingon the communication network design.

In the context of small cells, the FD modes provide enhanced benefitsdue to the small propagation delay (e.g., minor timing advance) whichmay be attributed to the relatively small distance between the smallcell network access node and the connected terminal devices. Small cellsmay be seen as being similar to WiFi access points, but they use LTEcommunication technology and have a range of roughly about 50 m to 100m. As a result, the uplink and the downlink paths are much smaller. InFD, the transmit and receive chains may be configured to be operate inthe same carrier frequency.

FIGS. 122-125 show exemplary scenarios implementing FD methods in someaspects, for example, with respect to communication network 100 showinga network access node 110 (e.g., a small cell network access node) and aterminal device 102.

FIG. 122 shows a first exemplary scenario implementing FD methods insome aspects of this disclosure. In FIG. 122 , the downlink (DL) pilotsymbols (12202 and 12204) are transmitted from the network access nodeto the terminal device (e.g., UE) and the uplink (UL) pilot symbols(12206 and 12208) are transmitted from the terminal device to thenetwork access node. The resources not occupied by the pilot/referencesymbols, e.g., the space between 12206 and 12208, may be reserved forcommunicating other data or information.

In FIG. 122 , the pilot symbols are full duplexed, so that thetransmissions and the receptions are performed at the same time at theterminal device side. The DL pilots and the UL pilots may be transmittedas orthogonal reference sequences to minimize the TX/RX co-interference(e.g., demodulation reference signal (DMRS)) and may be time/frequencyoverlapped only for the pilot symbols.

The terminal device may be configured to make use of the DL pilots(12202 and 12204) to perform a channel estimate and may use thisinformation to pre-equalize data sent in the UL. Based on the channelestimates determined directly from the DL pilots (12202 and 12204), theterminal device may pre-equalize the UL data symbols or may performother link adaptations, e.g., pre-coding or sub-band selection, for moreefficient and robust signaling with the network access node.Accordingly, one of the only delays the terminal device may experience,therefore, is the Rx signal processing delay, thereby facilitating thepre-equalization to be performed within a channel coherence time. Asimilar scheme may be implemented from the network access node point ofview, and in V2V and/or D2D communications in short ranges.

In some aspects, by implementing the FD mode at the small cell level,the pre-equalization may be performed by the small cell network accessnode, thereby simplifying the terminal device receiver design.Accordingly, the benefits of the FD methods and devices described hereinmay be most readily apparent in scenarios where devices are in closeproximity to each other, e.g., at the small cell level, D2D, V2V, etc.,due to the better performance gains which may be attributed to lower ULand DL interference.

FIG. 123 shows another exemplary scenario implementing FD methods insome aspects of this disclosure where devices are in close proximity toone another, e.g., small cell, D2D, V2V. As shown in FIG. 123 , thetiming advance is virtually non-existent, e.g., almost 0, and there is asmall power Δ between the TX and the RX. The UL reference symbols (12302and 12304) and the DL reference symbols (12306 and 12308) may beorthogonal sequences to further mitigate the transmissionself-interference, e.g., the transmitting devices may code divisionmultiplex (CDM) the reference symbols. The network access node transmits12306 and 12308 while simultaneously receiving 12302 and 12304,respectively, in order to estimate the channel transmission profile, H.Based on the channel estimate H from the reception of 12302, the networkaccess node may be configured to pre-equalize all symbols transmitted inthe DL in the slot N+1.

In some aspects, the devices may be further configured to perform apre-equalization. For example, with respect to FIG. 123 , the networkaccess node may boost the transmission power for deep fadedsub-carriers, thereby improving the signal to noise ratio (SNR) for thereceiver. Current conventional receiver side based equalization cannotachieve this. Furthermore, the network access node may be configured toperform phase pre-equalization, including phase rotation to account forfrequency offset errors. This simplifies the receiving device's basebanddesign and power consumption because the terminal device can potentiallyskip the channel estimation and equalization and directly proceed todemodulation of the received symbols. Additionally, the terminal devicemay use subsequent DL pilots symbols (e.g., 12308 in FIG. 123 ) tofurther improve channel estimations to help maintain or improveperformance. And, because the pre-equalization is performed within thechannel coherent time for the FD mode in devices which are in closeproximity, delays experienced are attributed to digital signalprocessing delays.

The schemes described with respect to FIG. 123 may also be applied fromthe terminal device to the network access node, or between terminaldevices operating in D2D and V2V communications.

FIG. 124 shows another exemplary scenario implementing FD methods insome aspects of this disclosure, extended from FIG. 123 . In FIG. 124 ,the UL reference symbols (12402 and 12404) are time and frequencyoverlapped (e.g., FD) with a subset of DL data symbols in Slots N andN+1. As shown in FIG. 124 , the network access point does not transmitreference symbols in the DL, instead using its resources fromtransmitting DL data payloads to increase DI throughput. The networkaccess node may be configured to perform a similar pre-equalizationprocedure to the DL data symbols as described with respect to FIG. 123 ,where the network access node pre-equalizes the data symbols instead ofthe respective pilot symbols, wherein the only latency is caused by thedigital signal processing delay. The terminal device DL receiver canthereby skip the channel estimation and equalization, and instead fullyrely on the pre-equalized data for subsequent demodulation.

FIG. 125 shows an exemplary scenario implementing FD methods in someaspects of this disclosure.

In FIG. 125 , the terminal device transmits UL reference symbols 12502and 12504, which are time and frequency overlapped with a subset of DLdata symbols. The UL data is transmitted in wideband, so that thenetwork access node can estimate all the sub-band channels and selectthe best sub-band channel for transmitting the DL data. The networkaccess node uses the received UL reference symbols for DL channelestimation and pre-equalization of DL data symbols, and also may furtherconfigured to use the received UL reference symbols to estimate the DLChannel Quality Indicator (CQI) and use it to optimize the DL modulationand coding scheme (MCS) and DL-sub band selection 12510. The MCS may beperformed according to a MSC index, e.g., BPSK (binary phase-shiftkeying) modulation types, QPSK (quadrature phase-shift keying)modulation types, 16-QAM (quadrature amplitude modulation), 64-QAM,etc., on different spatial streams, varying coding rates (e.g., ½, ⅔, ¾,⅚), and different data rates (which may depend on the channel).

In some aspects, the description in FIG. 122-125 may be extended to aplurality of terminal devices, where there is a power difference betweenthe reference signals from each of the multiple terminal devices and thenetwork access node. Accordingly, the terminal devices may be configuredto implement an iterative interference cancellation scheme in order tocancel reference signals from other terminal devices, so that thestrongest interference reference signal from another terminal device iscancelled first to produce a first interference cancellation productsignal, and after this first cancellation (i.e. first iteration of theinterference cancellation), then the next strongest interferencereference signal from another terminal device is cancelled (i.e. seconditeration of the interference cancellation) from the first interferencecancellation product signal of the first cancellation. This iterativeinterference cancellation scheme may be repeated for reference signalsfrom other terminal devices in order of diminishing interference for apredetermined number of iterations (e.g. any integer greater than 1).

FIGS. 126 and 127 show device configurations 12600 and 12700 forimplementing the FD methods in some aspects of this disclosure. Theseconfigurations are exemplary in nature and may thus be simplified forpurposes of this disclosure.

Device configuration 12600 shows a digital transmissionself-interference cancellation configuration for FD, when thetransmission and the reception has a lower power A, e.g., below 60 dBs.Device configuration 12700 shows a digital transmissionself-interference cancellation configuration for FD, when thetransmission and the reception has a higher power A, e.g., above 60 dBs.

The RF transmit (TX) chains in both configurations may include a digitalto analog converter (DAC), a low-pass filter (LP), a mixer (MIXER), anda power amplifier (PA). The RF receive (RX) chains may include a lownoise amplifier (LNA), a mixer, a LP, and an analog to digital converter(ADC). A local oscillator (LO) is also included to use with the MIXERsto modify the frequency of the signals.

Furthermore, configuration 12600 may include a transmit IQ buffer forreducing interference from the transmit chain from the received signal,while configuration 12700 may include radio frequency (RF) cancellationcircuitry for reducing the transmit interference from the receivedsignals.

In some aspects, a plurality of communication devices may be configuredto align their power levels for V2X multicast/broadcast in order tofacilitate FD (including the partial FD) operation between communicationdevices and/or network access nodes, or between terminal devicescommunicating in D2D and/or VRX scenarios. The clusters of power-alignedterminal devices may be grouped for each of respective network accessnode (e.g., small cell network access node), which may be either staticor mobile (e.g., located in a vehicle). This process may include a noderequest (e.g., from a terminal device, or a vehicular communicationdevice) to be part of a full duplex (FD) cluster, generation of acluster ID (if not already generated) or acquisition of an alreadygenerated cluster ID, and allocation of the node to the cluster ID. Anumber of nodes (e.g., other terminal devices, vehicular communicationdevices, infrastructure nodes such as road side units, etc.) may beallocated to a same cluster ID, wherein all of the nodes of the samecluster ID are within close proximity relative to each other in order tomatch their power levels for FD.

FIG. 128 shows an exemplary configuration of a terminal deviceconfigured to be a member of a cluster in some aspects. As shown in FIG.128 , the terminal device may include an antenna system 12802 and acommunication arrangement 12804, wherein the antenna system may beconfigured in the manner of antenna systems described within thisdisclosure (e.g., FIG. 2, 5, 6 ). The communication arrangement 12804may include an RF transceiver 12806 (which may operate in a similarmanner as described in, for example, FIG. 2, 5, 6 ), node clustermanager 12808, and/or node detector 12810. Node cluster manager 12808and node detector 12810 may be a physical layer, protocol stack, orapplication layer components, and, although not specifically limited toany particular implementation, may be part of one or more of a digitalsignal processor or controller of communication arrangement 12804 (e.g.,as in digital signal processor 604 and controller 606 of vehicularcommunication device 500).

The node cluster manager 12808 may be a processor configured to retrieve(e.g., from a local memory) and execute program code thatalgorithmically defines the management of node clusters in the form ofone or more executable instructions. For example, the program codeexecuted by node cluster manager 12808 may include a node managementsubroutine which may define a procedure for creating and/or receiving acluster ID from another communication device (or the network if withinnetwork coverage) and determining parameters for the management of thecluster, e.g., minimum power levels, GNSS position data, etc.

The node cluster detector 12808 may be a processor configured toretrieve (e.g., from a local memory) and execute program code thatalgorithmically defines the detection of other nodes in the form of oneor more executable instructions. For example, the program code executedby node detector 12808 may include a detection subroutine which maydefine a procedure by which a node may detect other nodes and/orclusters in order to generate a new cluster or join an already existingcluster and/or may also include a detection subroutine for a node of analready formed cluster to detect closely located nodes for inviting tothe formed cluster. This may include, at least, the transmission orbroadcasting of its cluster ID.

If there is network coverage, the network can handle the creation of thecluster ID and the allocation of nodes (including terminal devices) to arespective cluster ID, as shown in a message sequence chart 12900 inFIG. 129 . A node may send a request to the network access node, whichmay determine the power level attributed to the node based on therequest. Based on the determined power level and/or location of thenode, the network may either create a cluster ID if no cluster ID existsfor the determined power level, or allocate the node to an alreadycreated cluster ID based on determined power levels and/or location.Other nodes may be added to the cluster ID upon sending respectiverequests to the network and the network determining that the node meetsthe requirements (e.g., power levels and/or location via GNSS) forjoining a cluster. Alternatively, the network may initiate theassignment of a node to a cluster by identifying a node within a clusterID's coverage area using power levels and/or location (e.g., via GNSS)and sending a transmission to the node, including the cluster ID, withinstructions for joining the respective cluster.

If there is no network coverage, e.g., in V2X communications, severaloptions for the devices to negotiate the appropriate power levels to usein communications may be implemented wherein a master node assumes theresponsibilities of the network as shown in FIG. 129 . In a first optionsimilar to discovery in D2D communications, there is an exchange insignaling between devices where there is a message response to thecreation of a cluster ID by a master node, e.g., a terminal device or avehicular communication device. The master node may then assign thecluster ID and send out invitations to closely located nodes to join thecluster, or each node may be configured to determine which clusterprovides the best fit based on measured power levels (e.g., closest toits own power levels) and independently join the appropriate cluster.Other options may include utilizing geographic information (e.g., eachterminal device may receive its positioning from GNSS and/or map) inorder to form a cluster of closely located terminal devices. Furthersignaling (e.g., user ID and its geographic information) may betransmitted and included in the broadcasting signals associated witheach respective user ID/geographic information. Accordingly, the masternode may not be required in some aspects.

In some aspects, the FD mode is used for selection of a pre-codingmatrix indicator (PMI) at the network access node. In current LTEcommunications, the calculation of the PMI is performed subject to avery long delay since the network access node has to send a signal tothe terminal device, the terminal device performs a measurement on thesignal, and reports the measurement back to the network access node,which then applies the appropriate PMI values in subsequent DLtransmissions. This process may result in a delay, such as at least 8ms. By implementing the FD mode in some aspects of this disclosure, theterminal device may immediately derive the PMI after receiving the FDedpilots (e.g., as seen in FIG. 122 ). Similarly, the channel qualityindicator (CQI) may be determined by the network access node based onthe UL pilots and apply it directly to the DL signals (e.g., as seen inFIG. 125 ).

In some aspects, the devices may be configured to determine whether ornot the FD mode may be enable/disabled, or if the switch to another FDgroup may be required. The device may include hardware and/or softwareconfigured to detect the quality of the FD communications, and if the FDcommunication results in an error, the device may identify the source ofthe error (e.g., by identifying in which terminal device the erroroccurs), and exclude the terminal device from the FD group, e.g.,cluster. In some aspects, the identified terminal device may betransferred to another FD group (e.g., with a different cluster ID)where its communication properties may prove a better fit, e.g., similarpower levels and/or operating frequencies.

FIG. 130 shows a flowchart 13000 describing a method for communicatingbetween a first device and a second device in some aspects.

The method shown in flowchart 13000 may include: generating a firsttransmission symbol at the first device 13002; receiving a first signal,comprising a pilot symbol, at the first device from the second device13004; transmitting the first transmission symbol at the same time andfrequency as the received pilot symbol to the second device 13006;performing a channel estimate at the first device based on the receivedpilot symbol 13008; modifying a first data based on the channel estimate13010; and transmitting the modified first data to the secondcommunication device 13012.

FIG. 131 shows a flowchart 13100 describing a method for wirelesscommunications in some aspects.

The method shown in flowchart 13100 may include: transmitting an attachrequest from a first device to a second device 13102; determining acriteria for the attach request received at the second device 13104;assigning the attach request to a respective cluster identificationbased on the determined criteria, wherein the cluster identification isallocated a respective set of resources from a total resource pool13106; transmitting the cluster identification from the second device tothe first device 13108; and modifying the first device's transmissionand/or reception signal processing based on the cluster identification13110. In some aspects, the device state information includes locationinformation and/or information for determining a power of the signalingbetween the first device and the second device. In some aspects, themodified first device's signal processing may include the first devicetransmitting signals at a specified time and/or frequency.

Low Cost Broadcasting Repeaters

V2X is a multi-user broadcasting system, meaning that each user has todemodulate the signals broadcasted from multiple users at the same time,wherein each signal may have different time, frequency, and/or poweroffsets. As a result, there may be a wide range of varying signals(which are generally frequency-multiplexed) in a particular area at anygiven moment that a user may need to decode. In V2X or othergeographic-dependent scenarios (e.g., installation of small cells withinmacro cells), there is a need to provide for more efficient broadcastingin order to reduce the interference between signals. Furthermore, it isadvantageous to do so while maintaining a simple receiver design toreduce costs. Current conventional methods use dynamic beamformingarrangements, which are costly due to the multiple RF transmissionantennas which may need strict clock synchronization, complex front-endhardware, and geographical mapping.

To help address the aforementioned issues, an efficient broadcastinginfrastructure including low-complexity broadcasting repeaters (LBR) isimplemented to relay signals between terminal devices and/or othernetwork components, e.g., network access nodes. Broadcasted signals arereceived by these repeaters, which may be distributed around/along anarea of interest (e.g., a road) and have fixed antenna patterns forrelaying received signals. In some aspects, small cells may be deployedusing repeaters in order to minimize interference with existinginfrastructure, e.g., macro cells. As a result, the costs attributed todynamic beamforming may be reduced or altogether eliminated.Furthermore, these repeaters will provide for better regulation ofpower, time, and frequency and simplify V2X reception, since all of theTx terminal devices may be configured with similar power levels andfrequency offset.

FIG. 132 illustrates problems identified in V2X communications in someaspects of this disclosure. A problem case scenario is shown in 13200,while 13250 illustrates the frequency, time, and power imbalance fromthe different broadcasting vehicles in 13200. The different shadings in13250 represent different power levels.

As can be seen from 13200 and 13250, each of the users (e.g., vehicles)broadcast their V2X signals with imbalances in frequency, time, andpower between each of the broadcasted signals. For the four users, theoverall time and frequency resource pool of the broadcasted signals isshown on the right in 13250, which illustrates the multiple unbalancedparameters, which results in an increased complexity in processing forthe Rx demodulators for each of the users. There are various timeoffsets between the users, resulting in a non-optimal fast Fouriertransform (FFT) window for common frequency domain processing. Also, thefrequency offsets may result in inter-resource block interference, e.g.,as seen between User 3 and User 4 in 13250. Furthermore, the varyinglevels of received power levels of the signals between the users (shownby the different levels of shading) prevents a simple, optimal AutomaticGain Control (AGC) setting to satisfy the signals received from theother users.

FIG. 133 shows an exemplary network configuration 13300 and frequency,time, and power graph 13350 in some aspects. LBRs 13302 a-13302 e arearranged along the particular area of interest, in this exemplary case,a stretch of road, and are configured to receive signals broadcast fromvehicles, and use their fixed antenna patterns to repeat the receivedsignals towards each LBRs respective area of interest (shown by thedashed lines).

By implementing a network of LBRs 13302 a-13302 e, a terminal device(e.g., in this scenario, any one of vehicular communication devicesshown in 13300) may only need to transmit its signal to a nearby LBR.The location of each respective LBR of the LBR network may bestrategically chosen at launch in order for the LBR network to providefull coverage of the area of interest. Since the vehicular communicationdevice only needs to transmit its signal to the nearest LBR, a muchlower power is needed when compared to broadcasting the V2X signal to awider range of area. The LBR receives the transmitted signal from eachof the one or more vehicular communication devices, and repeats thesignal to its respective area (e.g., portion of road) and/or other LBRsdepending on its fixed antenna configuration. There is no need fordynamic beamforming at either the vehicular communication device or theLBR since the vehicle may be configured to transmit the short-rangebroadcast to the nearest LBR, and the LBR repeats this signal to otherdevices in the area (as well as LBRs within its network) according toits fixed antenna pattern. Accordingly, at deployment, each of LBRs'13302 a-13302 e location and antenna patterns are chosen andspecifically shaped to the area of interest, e.g., in 13300, with theenergy focused on the road.

FIG. 134 shows an exemplary internal LBR configuration 13400 in someaspects. It is appreciated that configuration 13400 is exemplary innature and may therefore be simplified for purposes of this explanation,e.g., each LBR will have a power source although not explicitly shown.LBR 13400 may correspond to each of LBRs 13302 a-13302 e shown in FIG.133 .

LBR 13400 may be configured at low complexity, with circuitry configuredfor physical layer signal repetitions (to repeat the received signalsfrom the terminal devices) and minimal waveform regulation circuitry forbalancing frequency/time/power offsets between the different receivedsignals.

LBR 13400 is fitted with an antenna 13402 capable of receiving signalsand transmitting signals in a fixed transmission signal pattern. Thefixed reception and/or transmission signal pattern may be set atdeployment by setting the antenna array in a manner which causesconstructive interference in the LBR's area of interest.

LBR 13400 may also include radio transceiver 13404 that may performtransmit and receive RF processing to convert outgoing baseband samplesfrom signal processing subsystem 13406 into analog radio signals toprovide to antenna system 13402 for radio transmission and to convertincoming analog radio signals received from antenna system 13402 intobaseband samples to provide to signal processing subsystem 13406.

LBR 13400 may also include signal processing subsystem 13406 forwaveform regulation circuitry 13408 configured to harmonize time,frequency, and/or power offsets from multiple vehicular communicationdevices before relaying the signals. This simplifies the V2X Rx designat the receiver side, while also providing for improved link robustness.Furthermore, because LBR 13400 is stationary, the maximum Doppler Shiftis reduced by 50%, further simplifying V2X Rx design while increasinglink robustness. The LBRs may be regulated/pre-allocated in terms ofpower, time, and/or frequency, and they may provide for easier relayingof regulated/synchronized signals since the LBRs are fixed head of time.

Waveform regulator 13408 may be structurally realized with hardware(e.g., with one or more digitally-configured hardware circuits or FPGAs,rectifiers, capacitors, transformers, resistors, etc.), as software(e.g., as one or more processors executing program code definingarithmetic, control, and I/O instructions stored in a non-transitorycomputer-readable storage medium), or as a combination of hardware andsoftware, in order to harmonize a plurality of signals received at theLBR 13400 from other terminal devices. Waveform regulator 13408 mayinclude a time offset corrector for correcting or adjusting a timeoffset among the plurality of signals. This may include first performinga time offset estimation which may include correlating the receivedframes in the plurality of signals with a known standard pattern at theLBR 13400, e.g., Primary and Secondary Synchronization Signals (PSS andSSS) in LTE, and performing the time offset correction based on the timeoffset estimation. Waveform regulator 13408 may include a frequencyoffset corrector for correcting the frequency offset among the pluralityof signals. The frequency offset corrector may be configured to performa frequency modulation of the signals including frequency offsetestimation and frequency offset compensation. Waveform regulator 13408may include a power offset correct for determining and resolving thepower offset among the plurality of signals, e.g., with a powerequalizer. In this manner, the LBR 13400 is configured to repeat theplurality of signals, which were received with differing levels ofpower, at a constant (e.g., equal) power level.

LBR 13400 may also include synchronizer 13410. In some aspects, varioussynchronization options for the LBRs are provided. The synchronizationmay be performed by a base station, e.g., eNB, (13304 in FIG. 133 )serving the area where the LBRs 13302 a-13302 e are located, e.g., theeNB may transmit the synchronization signals in the MIB and/or SIBs. TheLBRs may be configured to receive the synchronization signals from thebase station and relay them to their respective areas of interest. Thesynchronizer 13410 may be configured to receive and repeat thesynchronization signals received from the base station to its designatedarea of interest (e.g., according to its fixed antenna pattern).

In another aspect, the LBRs may be outfitted with Global NavigationSatellite System (GNSS) circuitry and be configured to synchronizeresources based on GNSS signals. In this aspect, the synchronizer 13410may include GNSS circuitry (e.g., GPS) for processing GNSS signals touse as the synchronization source.

LBR 13400 may also include a repeater 13412 configured to repeat thesignals which have been regulated by the waveform regulator 13408 andsend the signals to antenna 13402 for broadcasting according to the LBRsfixed antenna pattern.

In another aspect, the synchronization may be performed bysynchronization subframes communicated between the terminal devices(e.g., vehicles) themselves, e.g., via the PC5 interface in LTE D2Dcommunications. When a terminal device is reserving a resource, theterminal device may only be reserving it for a certain amount of time,e.g., when moving to another area, the terminal device may need torealign and synchronize with the respective LBR in that area. In orderto help avoid this, the terminal device itself could serve as thesynchronization source between a plurality of LBRs, where at least oneterminal device in each area served by an LBR maintains synchronizationin its transmissions, e.g., the LRB would repeat the transmissions, butthe original transmissions from the terminal devices would be bettermanaged. This would increase the complexity of the signal processing ateach of the terminal devices, since the LBRs would serve as repeaters ofthe terminal device monitored synchronization.

In some aspects, a synchronization option in which the LBRs act as thesynchronization source is provided. The LBR may be configured tobroadcast the synchronization signal based on its own internal timing,e.g., based on the LBR's own internal clock. The terminal devices willthen use this synchronization signal for frequency and time alignmentfor its communications with other devices. In this aspect, all of theterminal devices in the area may use the LBR as the synchronizationsource. The LBR may be configured to assign the highest synchronizationpriority for GNSS, and accordingly, be configured to search for a GNSSsignal first in a hierarchy for synchronization. If synchronization viaGNSS fails, the LBR may be configured to use other synchronizationsources, e.g., a base station, its own internal timing, etc.

Accordingly, an LBR may serve as the synchronization source for theparticular area (e.g., highway segment), and provide for resourceselection in the geographic area for the terminal devices located withinits area. LBRs may be configured to communicate (either wirelessly orvia direct physical interface) with proximate LBRs in order to maintainsynchronization of terminal devices moving along a path. If the LBRs arewithin communication range of each other, then they can automaticallymeasure the delta in the time alignment.

In some aspects, the type of synchronization signal may specify thesynchronization source, e.g., via GNSS or LBR timing. In any case, theLBRs are configured to receive and/or generate the synchronizationsubframes and repeat them to their respective areas and/or other LBRs.In this sense, the terminal devices may not be able to distinguish thatthe synchronization originates from an LBR instead of the eNB and/orother terminal devices.

In some aspects, the LBRs may be configured to identify a destination ofa message (e.g., received from a terminal device) or “how far” themessage should be transmitted, and transmit the message to proximateLBRs accordingly. In this manner, the LBRs may be configured to exchangeinformation with each other through wireless communication signals orvia a physical interface forming a network of LBRs.

FIG. 135 shows a flowchart 13500 describing a method for wirelesscommunications in some aspects of this disclosure.

The method may include receiving plurality of signals, wherein eachsignal of the plurality of signals is transmitted from a respectiveterminal device 13502; regulating the plurality of signals, wherein theregulation comprises harmonizing at least one offset among the pluralityof signals 13504; and broadcasting the regulated plurality of signalsover a fixed target area 13506.

In some aspects, the LBRs may also be used in initial small celldeployment. Small cells are typically deployed long after macro cellsare deployed, and therefore, may cause interference in the macro cellbeyond the geographical area of interest of the small cell.

FIG. 136 illustrates a small cell deployment problem scenario 13600. Asmall cell base station 13602 may deployed with a coverage area 13612ranging up to 200 m (e.g., for a pico cell) extending radially from thesmall cell. However, the small cell station 13602 may be deployed tocover a specific target area 13620, e.g., an office corridor and itsoffices. Accordingly, current conventional small cell deployment methodsmay cause small cell interference with an already deployed macro cell,for example, well beyond the target area 13620. This unnecessaryinterference beyond the small cell's target area is shown as the areawithin 13612 and outside of target area 13620. Typically, in order tomitigate or avoid this interference problem beyond the boundaries of thetarget area 13620, the macro cell and its associated coverage area wouldhave to be re-planned within the network, which is costly.

By employing small cells with a plurality of remote radio heads (RRHs),e.g., LBRs, the small cell may be deployed with energy focused specificto the target area, as shown in configurations 13700 and 13750 in FIG.137 .

As shown in 13700 and 13750, RRHs may be used to cover the areas ofinterest of the small cells while minimizing, or eliminating altogether,the interference macro cells outside of the area of interest. In thissense, there would be multiple RRHs associated with a common small cell,where the RRHs have a lower transmission power than a normally deployedsingle small cell station. The RRHs may be configured to transmitomnidirectionally (e.g., LBRS 13702 a-c), or in a fixed beamformingpattern (e.g., LBRS 13752 a-c). While shown in a two-dimensionalperspective, the small cell deployment discussed herein may be appliedto a three-dimensional setting as well (e.g., for drones and otherdevices).

One of the RRHs may be outfitted as the base station of the small cell.The small cell base station may be configured to coordinatecommunications across all of the RRHs and communicate with the mainnetwork, or there may be a separate network access node (not pictured)configured to communicate with the RRHs and the main core network. Eachof the RRHs are configured to transmit the same waveform, but may notneed to be clock synchronized, since they may be functioning more as awaveform repeater for the small cell which shapes the waveforms to thetarget area 13620. The small cell base station (e.g., small cell networkaccess node) may be configured as the synchronization source for thesmall cell communication arrangement of the RRHs.

Another benefit of deploying the small cells with RRHs is for bettercoverage and spectral efficiency resulting from multipath behavior ofthe plurality of RRHs, e.g., multiple instances of similar signals (fromeach of the RRHs) arriving at the UE at different times from differentlocations.

In some aspects, the terminal device will transmit its uplink (UL)signals to all of the RRHs of the small cell, providing receivediversity at the small cell. Each of the RRHs would provide the receivedsignals to the base station of the small cell, which locally processesthe signals. Alternatively, the terminal device may be configured totransmit the UL signals in a highly directional manner to a single RRH(e.g., the closest one), which then forwards the signal to the basestation of the small cell for further processing.

In some aspects, RRHs deployed in the small cell may be configured to beenable/disabled based on where terminal devices within the small cellare located. The RRHs and/or the small cell base station may beconfigured with a detection mechanism, for example, if a certain RRH hasnot received signals from a UE after a predetermined amount of time, thesmall cell may disable/power down that particular RRH. In anotherexample, the UE could provide feedback to the small cell that detailsthe current reception, and then the small cell could enable/disable theRRHs based on the feedback. In some aspects, the small cell may adaptthe RRHs to try to generate a single path (vs. multipath) at the UE,thereby allowing for a simpler design at the Rx side.

The small cell base station, therefore, may be configured to receivesignals from one or more terminal devices via the distributed RRHs, andmay be configured to observe which paths have the highest energy (e.g.,the RRH with the highest Rx power) in order to decide which RRHs may beenabled/disabled accordingly. By dynamically enabling/disabling (ortuning) the RRHs, the small cell station may further reduce interferencewith other previously deployed stations (e.g., for macro cells) evenwithin the target area 13620.

From the UE side, small cell deployment using a plurality of RRHs wouldbe similar to a large single-frequency network (SFN). However, largepropagation effects will not be needed to be taken into account due toshorter guard intervals. In some aspects, a UE may be configured with adetection mechanism in order to identify if it falls within a small cellemploying multiple RRHs. For example, in high-Doppler scenarios, the UEmay be configured to trigger multipath transmission and/or receptionwith the RRHs. Further, depending on which RRH has the highest Rx energyfrom the UE, the UE may be configured to request the right to a specificservice, e.g., operating at an increased communication distance to aparticular RRH if high-speed detected.

In some aspects, depending on the capabilities of the terminal device, aterminal device may be configured to operate as a small cell station(e.g., if configured as an LTE hotspot), and be configured to operateclosely located RRHs in the manners described above. In some aspects,the terminal devices themselves could serve as temporary RRHs configuredto provide additional coverage within the target area.

Such relays may also execute “transformation” (or “translation”)services from one radio access technology (RAT) to another. For example,a IEEE 802.11p based DSRC/ITS-G5 signal may be received by a relay, thedata content may be extracted and put into a LTE C-V2X packet and thenre-transmitted in the modified radio standard (or in both, C-V2X as wellas DSRC/ITS-G5).

FIG. 138 shows an exemplary scenario 13800 in which a node may beconfigured as a relay to execute transformation/translation servicesbetween different RATs in some aspects. It is appreciated that 13800 isexemplary in nature and may thus be simplified for purposes of thisexplanation. While shown as being a vehicular communication device FIG.138 , the following description of node 13802 may also be implemented instationary infrastructure elements, such as eNBs, RSUs, RRHs, or LBRs,etc. Node 13802 therefore may be configured to operate in several RATtechnologies in order to serve other terminal devices, e.g., vehicularcommunication device 13810 operating under the LTE C-V2X protocol andvehicular communication device 13812 operating under the DSRC/ITS-G5protocol, and provide a relay point of communication between the otherdevices. While shown as a terrestrial vehicle on a road in FIG. 138 ,the ensuing description with respect to node 13802 may also be appliedto other vehicular communication devices, e.g. drones.

In some aspects, if such a translation is required, node 13802 isconfigured to implement the full RX/TX chains of the respectivetechnologies as illustrated in the FIG. 139 (in this example, RAT 1 isDSRC/ITS-G5 and RAT 2 is LTE C-V2X, or vice versa):

Since the processing of RAT2 is expected to be repetitive is many cases,e.g., the similar preamble symbols, pilot tones, etc. are typicallyinserted in the same way, it may be possible to simplify the processing.Any part of the RAT2 frame which is always similar is pre-processed andits corresponding output samples (typically the inputs to the DAC of RFtransceiver, e.g., 204 in FIG. 2 ) are stored in a look-up table, whichmay be stored in a local memory component of the baseband modem (e.g.,206 in FIG. 2 ). Those parts which actually require processing of theinput data (typically operations such as channel encoding, etc.) will beprocessed. The results of the processed data are then inserted intoparts of the pre-buffered frame which are left empty for that purpose.Each of blocks A-E for RAT1 and RAT2 in FIG. 139 represent a processingblock for the respective RAT, and may include any of the signalprocessing functions described herein, including analog and digital RFfront-end processing circuitry to produce digital baseband samples andto produce analog radio frequency signals to provide to antenna, such asLow Noise Amplifiers (LNAs), filters, RF demodulators (e.g., RF IQdemodulators)), and analog-to-digital converters (ADCs); PowerAmplifiers (PAs), filters, RF modulators (e.g., RF IQ modulators), anddigital-to-analog converters (DACs). Blocks A-E may also represent aprocessing component for baseband modem functions, as error detection,forward error correction encoding/decoding, channel coding andinterleaving, channel modulation/demodulation, physical channel mapping,radio measurement and search, frequency and time synchronization,antenna diversity processing, power control and weighting, ratematching/de-matching, retransmission processing, interferencecancelation, and any other physical layer processing functions. Whilefive processing blocks are shown in each chain for RAT1 and RAT2, it isappreciated that this is done for exemplary purposes and that thedisclosure herein covers any number of processing units as needed forthe signal processing described herein.

FIG. 140 illustrates an exemplary device internal configuration 14000for processing different RAT signals in some aspects. Internalconfiguration 140000 assumes that the only required processing occurs inblock C and D of RAT2 and all the remaining operations lead to outputsamples that are always identical and can thus be stored in a look-uptable as previously described (e.g., preamble symbols, pilot tones,etc.). A determiner 14002 suitably manages the Multiplexer 14004 inorder to determine which inputs (results of processing elements oroutputs of the look-up table 14006) should be taken.

FIG. 141 shows a flowchart 14100 describing a method for deploying asmall cell communication arrangement in some aspects of this disclosure.

The method may include deploying a small cell network access nodeconfigured to provide access to a network 14102; and deploying aplurality of remote radio heads (RRHs) in communication with the smallcell network access node, wherein each of the plurality of RRHs isconfigured to serve as an interface for terminal devices in a respectivetarget area of the small cell with the small cell network access node14104.

FIG. 142 shows a flowchart 14200 describing a method for translating afirst radio access technology (RAT) signal into a second RAT signal insome aspects of this disclosure.

The method may include receiving a first RAT signal, wherein the firstRAT signal comprises unvarying symbols and unique symbols 14202;retrieving at least one second RAT symbol from the memory, wherein thememory is memory configured to store a look up table comprising secondRAT symbols corresponding to processed unvarying symbols of the firstRAT 14204; processing the unique symbols of the first RAT signal inorder to output corresponding symbols for the second RAT 14206; andcombining the retrieved at least one second RAT symbol with the outputcorresponding symbols to realize the second RAT signal 14208.

Small Cell Assistant UE In-Field Calibration

Generally, small cell stations include high-grade radio frequency (RF)components for communicating with terminal devices. Furthermore, thesmall cells may be configured to detect good channel conditions with oneor more terminal devices camped within its coverage. Terminal devicesare vulnerable to aging effects of their components over their lifetime,resulting in degradation of performance. For example, the degradation ofthe modem transistors leads to decreased switching speeds, andeventually, circuit failures. As the modem transistor scales to smallergeometries, the natural aging process of terminal device componentsaccelerates, further impacting performance.

Methods for in-field calibration of terminal device hardware arenon-existent as modem calibration is done in factory prior to devicedeployment. Since the calibrations are done prior to device deployment,these solutions do not account for the in-field aging effects on themodem hardware.

In some aspects, a calibration mechanism configures a small cell to testterminal device RF components in order to mitigate the aging effects ofterminal device modem hardware. The mechanism may include estimating theoffset of one or more modem RF components, and providing a correctivestep to eliminate/mitigate the offset. Optionally, the mechanism mayinclude determining a level of aging for different components in orderto implement a link selection algorithm to select the best link forcommunications. As a result, the lifetime of terminal device hardwaremay be extended.

Small cells stations target a smaller amount, but typically a moreconsistent identity of users (e.g., employees in an office setting),compared to macro cells. Because of this, small cells may not be as“busy” as macro cells, e.g., the small cells may have a time budget toprovide customized services to its terminal devices. Furthermore, due tothe closer proximity of the small cell stations to their users, thesmall cells provide increased Line-of-Sight (LoS) at highsignal-to-interference-plus-noise ratio (SINR) which may be exploitedfor terminal device calibration.

The small cell may be configured to broadcast calibration information,for example, in system information blocks (SIBs). This information mayinclude parameters for triggering a switch to calibration mode (e.g.,depending on SINR, terminal device status and/or position/movement, loadmonitoring information from the small cell and/or terminal device, etc.)and may further include specific calibration signal information, e.g.,resources on which the calibration signals will be transmitted. Cellspecific and static calibration (e.g., supported calibration modes by asmall cell) may be suitable for transmission over SIBs, while terminaldevice specification calibration information (e.g., selected calibrationmodes, calibration parameters, etc.) may be configured by RRC(re-)configurations (for semi-static cases) or Downlink ControlIndicator (DCI) from physical downlink control channel (PDCCH) (fordynamic cases) to the terminal device.

In some aspects, the terminal device and/or small cell are configured todetect appropriate channel scenarios to calibrate the terminal device.Parameters for detecting the calibration scenarios may include signalconditions meeting a certain threshold (e.g., signal quality above apredetermined value), determining when the small cell is not “busy”based on load monitoring, determining terminal device positioning andmovement (e.g., proximity to the small cell station and/or whether theterminal device is moving or stationary), etc. In addition, the terminaldevice may use embedded sensors, such as proximity sensor, gyroscope,and accelerometer, to further determine if the terminal device has anideal line of sight with the small cell. For example, using a gyroscopesensor, the terminal device can determine its location and space andverify the antenna is well positioned with respect to the small cellstation. In another example, using a proximity sensor, the terminaldevice can assess that it is located in an optimal open space and notwithin a pocket or jacket that may disturb the communication.

FIG. 143 shows an RRC state transition chart 14300 in some aspects ofthis disclosure. It is appreciated that RRC state transition chart 14300is exemplary in nature and may thus be simplified for purposes of thisexplanation.

Two RRC modes are introduced: RRC_DIAGNOSTICS mode and RRC_CALIBRATIONmode. In some aspects, these two modes may be merged into a single modeperforming the processes described herein.

The RRC_DIAGNOSTICS mode may be triggered by the small cell to one ormultiple terminal devices in order to enforce a diagnostic check at theterminal device (e.g., check filter shapes, out-of-band radiation,carrier frequency stability, etc.). In the RRC_DIAGNOSTIC mode, thesmall cell is used as a testing equipment to test the terminal device RFunit and decide whether it needs to go to RRC_CALIBRATION mode. In theRRC_CALIBRATION mode, the small cell can be further used as calibrationequipment to calibrate the terminal device RF if the diagnostics fail.

Once the terminal device and/or small cell determines that theappropriate conditions are met, the terminal device may be configured toswitch from RRC_CONNECTED mode to a RRC_DIAGNOSTICS mode. Suchconditions may be triggered from measured key performance indicators(KPIs) or the application layer may trigger the switch toRRC_DIAGNOSTICS. Other conditions for triggering a calibration of theterminal device may include the use of timers (e.g., a timer to triggera calibration after a certain period of time with respect to a previouscalibration. The KPIs may include frequency offset errors estimated bythe terminal device RX or small cell RX, error vector magnitude (EVM)measurements by the terminal device RX or small cell RX, Spurmeasurement in terminal device downlink RX, or the like.

In RRC_DIAGNOSTIC, the terminal device may run a self-diagnostic test,and report the results back to the small cell. This report may include adetailed report of the diagnostic test results, or it may simplyindicate whether or not calibration is required. If a component of therespective terminal device fails this diagnostics test (e.g., KPIs fallbelow a quality threshold), the RRC_CALIBRATION mode is triggered forcalibrating the terminal device.

FIG. 144 is an exemplary message sequence chart (MSC) 14400 showing aterminal device (e.g., UE) RX calibration in some aspects.

Upon failure of the diagnostics test in RRC_DIAGNOSTICS mode, a switchto the RRC_CALIBRATION is triggered. For terminal device receive (RX)calibration, the small cell transmits one or more calibration referencesignals to the terminal device. These calibration reference signals mayhave different waveforms than those in normal operations, e.g., singletones, dual tones, dual carriers, etc. The terminal device may beconfigured to iteratively adjust the RF RX parameters based on thereal-time evaluations of the KPIs for the received calibration signalsuntil the KPI requirement threshold is met. RF RX parameters may includeS-parameters for the antenna tuner (e.g., S11, S12, S22, etc.), LOfrequency tuning, analog gain values (which may be frequency banddependent and/or temperature dependent), or the like. Optionally, theterminal device can also be configured to request the small cell tomodify the calibration reference signals based on UE requirements (e.g.,calibration for different frequencies). While one calibration signal isshown in MSC 14400, it is appreciated that in most cases, there will bemultiple iterations of RF parameter adjustments in order to find thebest KPI. If the calibration is interrupted (e.g., due to mobility orenvironment changes), a switch to RRC_IDLE may be triggered (as shown inFIG. 143 ). A robust protocol is implemented to handle exceptions, e.g.,calibration is interrupted by mobility/bad channel conditions. Forexample, after the calibration process is finished with KPI passing acriteria, a certificate can be issued to the terminal device and thenthe terminal device is allowed to store all the updated RF parametersinto its nonvolatile memory. Otherwise, if an exception is detected inthe middle of calibration process (detected by time-outs or handshakingprotocols) which shows that calibration is interrupted, the terminaldevice can discard the new RF parameters and reverts back to RRC_IDLE.

While in RRC_CALIBRATION mode, the terminal device and/or small cell maybe configured to run a maximum number of calibrations, and upon reachingthis number, the terminal device may switch to RRC_IDLE mode in order toavoid running calibrations on an infinite loop (as shown in FIG. 143 ).

In some aspects for terminal device Rx calibration, the small cell maybe configured to transmit a plurality of calibration signals to theterminal device so that the terminal device may iteratively evaluate theKPIs for each of the calibration signals and adjust the RF RX parametersaccordingly. For example, the small cells are configured to transmit thecalibration signals in series so as to allow the terminal device toevaluate the KPIs and adjust the RF RX parameters for a firstcalibration signal prior to the small cell transmitting a secondcalibration signal of the series. Furthermore, once the terminal devicehas adjusted its RX parameters so that the KPI threshold is met, theterminal device may be configured to transmit a calibration completesignal to the small cell in order to trigger a switch back to RRCnormal/idle mode.

FIG. 145 is an exemplary message sequence chart (MSC) 14500 showing aterminal device (e.g., UE) TX calibration in some aspects.

For terminal device transmit (Tx) calibration in RRC_CALIBRATION mode,the terminal device is configured to transmit one or more calibrationreference signals to the small cell, which is then configured toevaluate the KPI metrics for the received calibration signal and providefeedback of the KPIs through downlink (DL) to the terminal device. Theterminal device then iteratively adapts the RF TX parameters accordinglyuntil the KPI threshold is met. Adjustable RF TX parameters may includeTX power offset, TX DC-DC path-delay (used for envelope tracking), TXpower amplifier (PA) distortion measurement (used for digitalpre-distortion). Similarly with respect to MSC 14400, while onecalibration signal is shown in MSC 14500, it is appreciated that in mostcases, there will be multiple iterations of RF TX parameter adjustmentsin order to achieve the best KPI. Also in RRC_CALIBRATION mode, theterminal device and/or small cell may be configured to run a maximumnumber of calibrations, and upon reaching this number, the terminaldevice may switch to RRC_IDLE mode in order to avoid runningcalibrations on an infinite loop (as shown in FIG. 143 )

Once the KPI threshold for the calibration is satisfied, either theterminal device or the small cell may be configured to terminate thecalibration process. For example, from the terminal device side, uponreceiving the DL with KPI metrics that meet the KPI threshold, theterminal device may be configured to transmit a calibration completesignal to the small cell, thereby terminating the calibration andswitching back to RRC_IDLE mode (or RRC_CONNECTED mode).

In some aspects, the terminal device Rx and/or Tx calibration may beperformed in at least two operations: offset determination and offsetcorrection; alternatively, a third operation may be added so that thethree operations are: offset determination, determination of themalfunctioning source component, and offset correct. The offsetdetermination is determined by the evaluation of the KPIs of thecalibration reference signals (e.g., frequency shift due to oscillatoraging, etc.). The offset determination (or the determination of themalfunctioning source component) may, for example, search for one ormore faulty hardware components (e.g., degraded low noise amplifiers,aged power amplifiers, over-drifted oscillators, faulty decoders, etc.).The offset correction is performed by adjusting the necessary parametersin order to meet a KPI threshold, e.g., tuning of the oscillator,rerouting a degraded power amplifier to another power amplifier, etc.

While the detection of the aging effect of device components istypically used in order to mitigate a problematic behavior of a device,this detection may also be exploited in the offset determinationoperation for other purposes.

In an example, this detection may be exploited if the aging effects ofcritical components are too large, e.g., a large frequency shift due tooscillator aging, the entire TX path may be shut down (or in severecase, the entire equipment) in order to avoid damage to othercomponents.

In another example, this detection may be exploited if the aging effectsof critical components are too large, e.g., large frequency shift due tooscillator aging, the choice of frequency bands to be used may belimited. For example, if there are neighboring safety criticalapplications, the determined aging components will not be allowed tooperate in direct neighboring frequency bands to such safety criticalfrequency bands.

In a further example, a request to the “other end” of the TX/RX chain(e.g., the target RX in case of TX functions being executed by the agingdevice; or the target TX in case of RX functions being executed by theaging device) to implement some mitigation. For example, in case of afrequency shift by ΔF due to oscillator aging, the other end may beasked to apply the negative shift −ΔF in order to mitigate the shifteffects for the TX/RX chain. Alternatively, parts of the effects may behandled by the “other end” of the TX/RX chain and the remaining parts bythe aging device. For example, in case of a frequency shift by ΔF due tooscillator aging, the other end may be asked to apply the negative shift−ΔF/2 in order to mitigate the shift effects for the TX/RX chain and theremaining shift of −ΔF/2 may be done by the aging device itself.

If a malfunctioning source component is determined (e.g., due to agingeffects), it may be replaced. This replacement may be done according toseveral options as shown in the following figures.

FIGS. 146 and 147 show diagrams for an exemplary softwarereconfiguration based replacement of defective source components in aterminal device 14600 in some aspects.

The terminal device 14600 may include original components which supportone or more RATs, e.g., three RATs are illustrated in FIGS. 146 and 147: RAT 1, RAT 2, RAT 3. A number of RAT-specific components (analogand/or digital) may be included to support each RAT (e.g., for RAT 1:RAT 1 A, RAT 1, B, . . . , RAT 1 E) as described herein, e.g., RFtransceiver 204 and baseband modem 206 description in FIG. 2 . Forexample, each of these RAT-specific components may be, for example, acyclic redundancy check (CRC) generator/checker, channelencoder/decoder, interleaver/de-interleaver, constellationmapper/demapper, modulator/demodulator, encryption/decryption units,MIMO processors, etc.

Reconfigurable Controller 14602 may be configured to receive thediagnostic and/or calibration data from the tests run on RRC_DIAGNOSTICand/or RRC_CALIBRATION modes in order to identify faulty components. Forexample, if RAT 1 fails its diagnostics test in RRC_DIAGNOSTICS mode,and the subsequent calibration in RRC_CALIBRATION mode identifies thatRAT 1 B is the faulty component after performing the terminal deviceTX/RX parameter adjustments, e.g., there is too much phase noiseinjected, there is a frequency shift due to an aging oscillator, thereare memory access problems, insufficient/degraded power amplification,etc.

Upon identification of the faulty component, e.g., RAT 1 B in FIG. 147 ,the Reconfiguration Controller 14602 may be configured to replace thefunctionality of the components via rerouting the inputs and outputs,respectively, to a shared computational memory resource module 14604. Inthis respect, a key feature of this disclosure is properly defining theinputs/outputs, e.g., “bypass points,” of the specific components, shownas circles in the figures. Bypass points may be located at theinput/output of a particular component performing a specific operation,e.g., fast Fourier transform (FFT), turbo encoder, decoder, interleaver,MIMO encoder/decoder, etc. The shared computation memory resource module14604 may include FPGAs, DSPs, or other components, some of which may beinitially unused, but over time, may be activated to implement updatesor new features. Over the lifetime of the equipment, the ReconfigurationController 14602 may replace the identified faulty RAT components withsoftware blocks installed onto the reconfigurable computationalresources by rerouting the inputs/outputs of the component to the sharedcomputational memory resource module 14604.

FIG. 148 shows an exemplary diagram 14800 illustrating hardwarereplacement of defective source components in a terminal device 14802 insome aspects.

The terminal device, for example a UE or any other device, includes aplug-in slot where a plug-in card 14804 can be inserted providing newcomputational resources 14806 (e.g., memory or processing) and/or RFresources 14808 that can be used in order to replace malfunctioningcomponents. Then, such a replacement of functionalities is done similarto the SW reconfiguration case illustrated in FIGS. 147 and 148 . Thedifference is that the new components are not necessarily executed assoftware code loaded in the shared computational memory resource module14604, but actual hardware components (such as a new oscillator, a newfilter, etc.) are provided by the plug-in card 14804 and will replacethe aging component(s) as shown in FIG. 149 . The ReconfigurableController 14602 functions as described above with respect to FIGS. 147and 148 .

In some aspects, a combination of the aspects shown in FIG. 147-149 maybe achieved. The plug-in card 14804 provides additionalcomputational/memory resources for the execution of software code. Then,the aforementioned process is executed on these new resources madeavailable through the plug-in card.

In some aspects, communications of radio link control (RLC) messages maybe chosen based on the aging of different RAT hardware options, e.g.,RAT 1, RAT 2, or RAT 3 shown in FIGS. 146-147 and 149 . The KPIs takenduring the calibration stages for the different RAT hardware may bestored and taken into account when deciding which options to elect whenhandling different signals. For example, in V2X communications, theterminal device may choose between sidelink communications, V2Xcommunications, etc. Depending on the aging based performancedegradation of some of the RAT link choices, the terminal device isconfigured to select the best RAT choice possible. For example, if aDSRC sidelink hardware is degraded due to aging, the terminal device isconfigured to select LTE C-V2X sidelink or V2I/V2N to transmit acommunication instead.

The aging levels of different RAT hardware may be classified into one ofa plurality of levels based on their respective KPIs. These levels mayinclude one or more of the following: low aging (e.g., good for use),medium aging (e.g., attempt other RAT hardware options, especially forhigher priority safety features), high aging (e.g., may be limited tonon-safety features), and severe aging (e.g., not suitable for use).Accordingly, a terminal device may be configured with a link selectionalgorithm including programmable instructions retrieved from a memoryand executable by a processor to implement a process which takes theaging levels of different RAT components into account in order to selectthe most appropriate option for transmitting a communication.

In some aspects, the small cells may be configured to verify with thenetwork (e.g., via a macro cell) that the small cell is both trustworthyand working properly in order to perform the terminal device calibrationmechanisms of this disclosure. The small cell may be configured totrigger a testing mechanism with the macro cells, wherein the macro celltests the small cell to ensure that its calibration signal processingcomponents are functioning properly. This testing may be triggered basedon a timer (e.g., with respect to a previous testing) or based on anamount of terminal device calibration procedures the small cell hasperformed. This testing may be similar to that described above betweenthe terminal device and the small cell (e.g., an iterative testingprocess between the small cell and the macro cell) and once the smallcell passes the testing process, the small cell may receive acertification to communicate with terminal devices that it is approvedto perform calibration. The small cell may be configured to broadcastits calibration capabilities to nearby terminal devices. In someaspects, certain small cells may be authorized to perform certain typesof calibration (e.g., for a specific RAT frequency) and broadcast toterminal devices the calibrations that they are configured andauthenticated to perform.

FIG. 150 shows a flowchart 15000 describing a method for calibrating acommunication device in some aspects.

The method may include triggering a transition to an RRC diagnosticsmode, wherein the RRC diagnostics mode comprises determining a status ofone or more signal processing components of the communication device15002; determining whether the status passes or fails an evaluationcriterion 15004; upon the status failing the evaluation criterion,switching to an RRC calibration mode, wherein the RRC calibration modecomprises communicating one or more calibration signals between thecommunication device and a network access node 15006.

FIG. 151 shows an exemplary flowchart 15100 describing replacing acomponent of a communication device in some aspects.

The method may include: identifying the component as being defectiveaccording to the processes described in this disclosure (e.g., FIGS. 143and 150 ) 15102; loading one or more replacement components onto asoftware reconfigurable resource of the communication device 15104; androuting an input of the identified component to the softwarereconfigurable resource and an output of the software reconfigurableresource to a destination of the identified component output so that theone or more replacement components of the software reconfigurableresource replaces a functionality of the identified component 15106.

FIG. 152 shows an exemplary flowchart 15200 describing a method forselecting a RAT link for transmitting a message (i.e. link selectionalgorithm) in some aspects. The communication device may support aplurality of RAT links, e.g., is capable of communicating according toseveral RAT protocols, e.g., LTE, CDMA, WiFi, etc.

The method may include determining a status of each of a plurality ofRAT links of the communication device 15202, ranking the determinedstatuses of the plurality of RAT links 15204; and selecting a RAT linkto communicate a message based on the ranking 15206. The status of eachof the plurality of RAT links may be determined based on KPIs, and theranking of the plurality of RAT links may include, for example, rankingthe plurality of RAT links based on each of the RAT link's respectivestatus.

Customized Services/Radio Resources Optimization for Specific Users inSmall Cells

Small cells typically have a number of users which are camped on thesmall cell at routine times, e.g., employees in an office during officehours, residents in a residential building after work, etc. These usersmay use the resources from the small cell in a regular manner, and insome cases, the small cell may not be configured to provide these userswith the necessary resources as required. In some aspects of thisdisclosure, the small cells are configured to account for user or usergroups usage patterns in order to provide customized services and/orradio resources.

Conventional small cells, including those not configured based on thedisclosure herein, serve all users equally and the small cellconfiguration is based on instantaneous load measurements. Typically,past observations on the behavior of a user or user Group are not takeninto account. However, according to some aspects of this disclosure,knowledge of the behavior and typical requirements of specific usersand/or user groups may substantially support small cell configurationsin terms of efficiency, power consumption, etc. Since conventional smallcells do not exploit this knowledge, their final configuration willtypically be less efficient.

In some aspects of this disclosure, regular (in the ensuing description,regular when used to describe a user and/or device means routine orconsistent) small cell users are identified and provided with customizedservices and/or radio resources in order to provide a better userexperience. The small cells are configured to identify these users basedon user criteria and provide the identified users with the appropriateresources, link adaptation, and/or customized services based on acquireduser historical information. This may include the small cells beingconfigured to identify a subset of users and dynamically provide theseservices based on user activity. Furthermore, identified users mayreserve small cell radio resources in anticipation in order to provide abetter user experience. By identifying regular users and using theirpast behavior, small cells may provide optimal resource allocation, linkadaptation, and/or customized services.

The small cells are configured to learn terminal device behavior inorder to provide more reliable resource scheduling, link adaptation,and/or customized services for the identified regular terminal devices.When a terminal device attaches to a small cell, the small cellregisters the terminal device with the network (e.g., RRC connection,RACH procedure, NAS attach, etc.), and the small cell is furtherconfigured to identify the terminal device as a “regular” based on usercriteria. The small cell may identify a respective terminal device as aregular terminal device if the small cell has observed a routine patternof the respective terminal device camping on the small cell. This mayinclude time information including identifying start times, end times,durations, etc. for which the terminal device has camped on the smallcell, and may further include usage information including patterns ofresource usage by the terminal device. Using this observed behavior, thesmall cell may be able to identify regular terminal devices in order toprovide these terminal devices with optimized resource scheduling.

The classification of users may be done on a per-user basis or aper-user group basis.

For classification done on a per-user basis, the classification caneither be determined by the small cell itself or by the user (e.g., viathe terminal device). If it is determined by the user, the user maychoose a certain “User Category” out of a set of predetermined usercategories or the user can define a new category. Such user categoriesmay, for example, be as follows: a) user requiring low latency, b) userrequiring high data rate, c) user requiring Transmission ControlProtocol (TCP) traffic, d) user requiring User Datagram Protocol (UDP)traffic, e) user substantially occupies the medium, f) user onlysporadically occupies the medium, g) user typically uses a Videoservice, h) user typically visits Internet web pages, i) user is aprofessional user, j) user is a private user, k) user is of lowcommercial value (for delivering publicity, etc.), l) user is of mediumcommercial value, m) user is of high commercial value, etc. Thesecategories may be combined, depending on the user determination. It isappreciated that the above list is not exhaustive in nature and isintended to illustrate the wide range of possible user categories.

Depending on the one or more categories chosen by the user, the smallcell will adapt its operation correspondingly. In case that the userdefines a novel user category himself, such a category may includeoptions such as peak data rate requirements, average data raterequirements, peak latency requirements, average latency requirements,how often is the user accessing the medium, etc.

If the classification is done by the small cell, the small cell willobserve typical user behavior such as peak data rate requirements,average data rate requirements, peak latency requirements, averagelatency requirements, how often is the user accessing the medium, etc.and store the observations in a memory, e.g., a local memory, on thecloud, etc. Depending on those observations, the small cell will assigna user category to the target user, such as one or more of thecategories listed in above or other categories such as a low-end user(e.g., minimal resources needed), a medium user, a high-end user (e.g.,resource heavy user), etc. Once this category allocation is done, it canbe optionally provided to the user. The user may exploit the category,request a change of category, accept the category, reject the categoryand request and a new evaluation, etc. The category allocation may beshared (by the small cell and/or by the user) with other small cellsand/or other network entities in order to ensure an (a-priori) optimumconfiguration for the user while he is using a new or different smallcell (or other network element). In some aspects, this category may becommunicated to the new or different small cell (or other networkelement) in anticipation of the user arriving at the new small cell,e.g., based on tracked user movement. Accordingly, the small cell maypertain to a network of small cells which may be further configured toshare user information so that information for an identified regularuser of one small cell may be shared with another small cell to governits own communication with the user.

If the classification is done on a per-user-group basis, a target useris first characterized (following, for example, the classificationapproach outlined above for the classification on a per-user basis).Then, the small cell may identify one or multiple (either pre-defined ornewly defined) user-group classes to which the user may fit, e.g., basedon its identified user category. The user is then allocated to thisgroup and the small cell implements the appropriate network changesand/or network strategies (such as resource allocation, e.g., higher orlower bandwidth, media accelerators, etc.) may be performed on theuser-group level, not on a user level. Once this User-Group allocationis done, it can be optionally provided to each of the users. The usermay exploit the allocation, request a change of allocation, accept theallocation, reject the allocation and request a new evaluation, etc. Theallocation may be shared (by the small cell and/or by the user) withother small cells and/or other network entities in order to ensure an(a-priori) optimum configuration for the user while he is using a new ordifferent small cell (or other network element) or even before the useris arriving at a new or different small cell (or other network element)as described above.

Based on the criteria observed by the small cell for the identifiedregular users, the small cell may be able to forecast usagecharacteristics, and assign resources and/or set link adaptionaccordingly. When a users terminal device initially attaches to thesmall cell, the small cell may use information derived from pastsessions to communicate with the terminal device. The small cell mayprovide a semi-static link adaptation based on the historicalinformation for one or more of its regular identified terminal devices(users) instead of a real-time link adaption. For example, in the officesetting, a user may spend most of its time in a specific location (aparticular office), and the small cell may use past link-adaptationparameters (modulation, coding, other signal and protocol parameters)from when the user was in the specific location in order to transmitand/or receive signals to/from the user's terminal device.

In some aspects, a small cell is configured to observe the requirementsfor a specific user and/or user-group in a session. The optimumconfiguration for the user/user group network requirements is determinedand stored in a database. The database may contain information elementssuch as:

-   -   ++++++++++++++++++++++++++++++++++++++++++++++++    -   +User/User Group ID+Configuration requirements/preferences+    -   ++++++++++++++++++++++++++++++++++++++++++++++++

Accordingly, in the user/user group's next session on the small cell(or, alternatively, another small cell which has access to the (shared)database), the database information is retrieved and the previouslydetermined optimum configuration may immediately be applied. Over time,the user/user group behavior may change, at which point the user/usergroup may be re-classified to a different user/user group categoryand/or the configuration preferences/requirements for current categorymay be modified and updated in the database.

The access to the database may be authorized to other small cells andother network elements. This authorization may be done by a 3^(rd) partywho receives the authorization by an authorized small cell or by theuser itself (upon request by a small cell to access the database or by atrigger issued by the user, e.g., by instructing a small cell or othernetwork element to access to the database).

FIG. 153 shows an exemplary Message Sequence Chart (MSC) 15300 with acorresponding small cell network 15350 in some aspects.

In MSC 15300, one or more terminal devices attach and register with thesmall cell. The small cell is configured to identify the terminal deviceas a regular user based on a user criteria, e.g., based on pass userbehavior and sessions on the small cell. According to the user criteria,the small cell is able to determine the terminal device's usagecharacteristics and allocates resources, services, and/or linkadaptation based on the terminal device's past usage characteristics.This may include, for example, identifying the terminal device andretrieving its user category (or similarly, identifying the user groupand retrieving the user group category) and the category's operatingcharacteristics (e.g., bandwidth, usage rates, latency requirements,etc.) from the database.

In some aspects, the small cell may be configured with a terminal devicepriority determiner that may prioritize the allocation of resources toregular users over non-regular users (e.g., the white terminal devicesin 15350), but may still allocate resources to non-regular users. Inthis manner, while prioritizing the assignment of resources and/orproviding customized services to the regular users, the small cell isstill configured to provide resources for non-regular users that attachto the small cell in order to meet wireless protocol standards.

For example, in small cell network 15350, each of the black terminaldevices may be identified as regular users by the small cell. The smallcell may therefore be configured to retrieve each of the terminaldevice's user categories from its database and provide each of theterminal devices with resources respective to its user category asdescribed above. For example, for downlink, based on terminal devicefeedback from the previous session, the small cell is configured tolearn the terminal device resource usage characteristics and setscheduling policies accordingly, e.g., longer downlink periods toidentified regular terminal devices that consume more data. In uplink,for example, the small cell may set a schedule with the terminal devicefor the terminal device to manage its power control in a manner thatprovides for higher uplink throughput.

In another aspect, the small cell may collectively identify the blackterminal devices as pertaining to a specific user group category, andaccordingly, the small cell may be configured to assign resources to theusers in the user group pursuant to the information retrieved from thatuser group's category from the database. The small cell is configured toidentify one or more terminal devices as regular terminal devices andobserve their behavior to recognize the performance of repetitive tasks,and implement a dynamic provisioning of accelerators for these tasks.For example, if the small cell identifies a group of terminal deviceswhich are uploading photos, the small cell is configured to assign oneor more media accelerators tailored for this operation. The small cellidentifies calculation patterns for the identified repetitive task, andcaches the calculations and/or outputs for future use. The small cell isconfigured to identify these repeated tasks and provide a configurationcore (e.g., FPGA, or the like) to provide the necessary resources forthe dedicated accelerator tasks. Additionally, the small cell may beconfigured to assign resources based on a priority scheme. This priorityscheme may initially be set, but the small cell may be configured toadapt the priority scheme based on the resource usage of its identifiedregular users. For example, the small cell may be configured toprioritize the assignment of resources for videoconferencing over musicstreaming in an office setting.

In order to achieve these tasks, the small cell may be provided with“spare” computational resources, such as memory resources, DSPresources, FPGA resources and/or other processing resources.Additionally, these resources may be available remotely (for example inthe Cloud), in a neighboring Small Cell (through sharing of resourcesfor example) or in user terminal devices. As the small cell observesbehaviors of its regular users, the small cell may be configured to usethese computational resources in order to provide for a more tailoredservice to its regular users. FIGS. 154 and 155 provide exemplaryillustrations for this principle. It is appreciated that FIGS. 154 and155 may only include small cell elements necessary for purposes of thisexplanation.

Initially, the small cell 15400 is configured with spare/sharedcomputational/memory resources 15404, which may be unused by theoriginal transmission/reception chains, shown as RAT 1, RAT 2, and RAT3, each shown with five (A-E) analog/digital processing components. Eachof these analog/digital processing components may be configured toperform a RAT-specific task, for example, including any of the signalprocessing functions described herein, including analog and digital RFfront-end processing circuitry to produce digital baseband samples andto produce analog radio frequency signals to provide to antenna, such asLow Noise Amplifiers (LNAs), filters, RF demodulators (e.g., RF IQdemodulators)), and analog-to-digital converters (ADCs); PowerAmplifiers (PAs), filters, RF modulators (e.g., RF IQ modulators), anddigital-to-analog converters (DACs). Blocks A-E may also represent aprocessing component for baseband modem functions, as error detection,forward error correction encoding/decoding, channel coding andinterleaving, channel modulation/demodulation, physical channel mapping,radio measurement and search, frequency and time synchronization,antenna diversity processing, power control and weighting, ratematching/de-matching, retransmission processing, interferencecancelation, and any other physical layer processing functions. Whilefive processing blocks are shown in each chain for RAT 1-3, it isappreciated that this is done for exemplary purposes and that thedisclosure herein covers any number of processing units needed for thesignal processing.

The small cell includes a reconfiguration controller 15402 which isconfigured to identify regular users into respective user/user groupcategories and provide resources based on the necessary requirements forthe user/user group categories. When a particular requirement isidentified, the reconfiguration controller 15402 is configured to usethe spare/shared computational/memory resources 15404 to introduce a newfeature to support the particular requirement. For example, in diagram15500, the reconfiguration controller 15402 identifies that anaccelerator 15502 is needed between processing blocks A and B of RAT 1,and configure a processing core (e.g., FPGA, DSP, or the like) availablefrom the spare/shared computational/memory resources 15404 to providethis function accordingly.

Alternatively, as shown in 15550, the reconfiguration controller 15402may be configured to fully replace a component 15552, e.g., anoutdated/faulty accelerator, with a new accelerator 15554. Thereconfiguration controller 15402 is configured available processingcores (e.g., FPGA) from the spare/shared computational/memory resources15404 to provide a replacement accelerator 15554, and reroutes theinputs and outputs (using bypass point shown by the dark circles) of thefaulty component 15552 to the replacement component 15554 accordingly.

In some aspects, the small cell is configured to allow regular users toreserve or request resources from the small cell in advance. Forexample, a regular user may want to use video resources from the smallcell, and the small cell may be configured to allocate the appropriateresources for the terminal device in order to avoid real-time adaptionsince the resources and link-adaptation can be set in advance at thetime of the reservation or request.

In some aspects, the small cell may be configured as a neural network,and may adapt its resources to best serve the identified users which itregularly serves. For example, the small cell may be configured to takeas inputs the identified regular users, their usage of resources, timeinformation, etc. in order to output the resources to be allocated at aspecific schedule.

In some aspects, based on the identified locations of the regular users,the small cell may be configured to modify its broadcasting mode. Forexample, the small cell may be configured to pool information from agroup of closely located, regular users in order to broadcast data tothe group.

For a network of small cells, each small cell may be tailored specificto a particular service (e.g., one small cell for videoconferencing,another for music streaming, another for voice traffic, etc.) and beconfigured to direct identified users to the appropriate small cellconfigured to provide the required services. Each specialized small cellcan optimize the air resource allocation and the transmissionparameters. For instance, a small cell specialized for high throughputcan allocate the complete bandwidth to an identified user, thereforeenabling high throughput and also reducing the interface so that noother user is served in parallel. It can also pre-allocate resource foracknowledgment packet such as TCP high (TCP is sensitive to delay ordrop of TCP ACK). In another example, a small cell specialized for voiceover IP call can have periodic resource pre-reserved. The small cellconfigures semi-persistent scheduling (SPS) for all users connected tothe small cell. This allows for better usage of the radio resources asthe control signaling is reduced to its minimum (no scheduling requestrequired for each new terminal device transmission). This alsosimplifies the processing from the radio scheduler of the small cell,enabling a better dimension of the required hardware.

A network of small cells may further be configured to share userinformation so that information for an identified regular user of onesmall cell may be shared with another small cell to govern its owncommunication with the user.

FIG. 156 shows an exemplary small cell network 15600 with a plurality ofspecialized small cells in some aspects.

Small cell network includes a master cell 15602, which among otherthings (e.g., providing basic coverage to users camped on it), may beresponsible for the coordination of the specialized small cells. Themaster cell 15602 may offer a larger coverage as shown in 15600 and mayredirect terminal devices to a specialized small cell according to theterminal devices needs.

Two types of dedicated specialized small cells are shown in 15600:dedicated small cells for voice services 15612-15616 and dedicated smallcells for high data throughput 15622-15624. It is appreciated that othertypes of dedicated small cells may be implemented, such as dedicatedsmall cells for a particular media type, etc. The dedicated small cellsfor voice services 15612-15616 may be configured to optimize radioresource scheduling particular to voice data, while the dedicated smallcells for high data throughput 15622-15624 may be configured to optimizescheduling for high data throughput (e.g., enhanced bandwidth, moretransmission time intervals (TTI)).

As such, the master cell 15602 may be configured with a controllerconfigured to identify a request from a user and identify the respectivesmall cell to which the request is sent.

FIG. 157 shows an exemplary MSC 15700 for the signaling of a small cellnetwork in some aspects.

Upon the terminal device sending the Master Cell a service request,e.g., for Service X, the Master Cell identifies that the requestidentifies a high data throughput requirement which the Master Cell maynot be able to serve. Accordingly, the Master Cell identifies thededicated cell for this type of request, and redirects the terminaldevice to the appropriate Dedicated cell. The terminal device redirectsits Service Request for Service X to the Dedicated cell, which initiatesthe session. The Dedicated cell may be configured to provide resourcescheduling optimized for high throughput, e.g., reserving the fullbandwidth for one terminal device for one or more Transmission TimeIntervals (TTIs).

FIG. 158 shows a flowchart 15800 describing a method for a networkaccess node to interact with users in some aspects.

The method may include identifying one or more regular users based onuser criteria 15802; determining usage characteristics of the identifiedone or more regular users 15804; and allocating resources of the networkaccess node, providing a specific service, or performing a linkadaptation based on the usage characteristics 15806.

FIG. 159 shows a flowchart 15900 describing management of a networkaccess node arrangement including a master network access node and oneor more dedicated network access nodes in some aspects.

The method may include receiving, at the master network access node, aservice request from a terminal device 15902; identifying, at the masternetwork access node, a respective dedicated network access from the oneor more dedicated network access nodes configured to provide the requestservice 15904; and redirect the terminal device to the respectivededicated network access node 15906. In some aspects, the master networkaccess node may require that each of the dedicated network access nodesreport the services that they are optimized at in order to join thearrangement. Alternatively, the dedicated network access nodes mayautomatically report this at deployment. In any case, the master networkaccess node is configured with a database with its dedicated networkaccess nodes and their respective capabilities.

Personalization of Small Cells Through Software Reconfiguration

Mobile devices can be personalized through Apps from an App Store.However, small cells have not previously been able to be personalized.Because small cells are often owned and/or operated by private entities(e.g., in an office, residence, vehicle, etc.), it may be beneficial topersonalize these small cells specific to their usage.

In some aspects, two different types of Apps for small cellreconfiguration are provided: i) Non-Radio Apps (such as Android Apps)providing video games, tools, etc. and ii) Radio Apps introducingchanges of radio features, such as the addition of a novel Radio AccessTechnology (RAT), replacement of a component through a software versionof the same component (e.g., to resolve vulnerabilities of communicationcomponents).

Manufacturers may propose updates or modifications on demand which maybe provided i) through SW updates or ii) through HW changes incombination with SW updates. Methods offered to the small cell users maybe elementary updates (e.g., updates by manufacturers) which are appliedto a given type of equipment. The availability of such updates may behard to anticipate and may not be based on the small cell's users'needs.

In some aspects of this disclosure, tailoring of the features of thesmall cell to the needs of the small cell user is achieved. Accordingly,the small cell can thus be adapted to the specific needs of a user inreal-time. The small cells are fitted with software reconfigurableresources in order to allow users to personalize them specific to theirneeds. A user can choose software components (e.g., Apps) which are thenuploaded and installed on the small cell or a network of small cells.Such Apps can provide features on a single, multiple or all ISO layers,such as an Application Layer operation and/or Lower Radio Layers forsoftware reconfiguration components provided by third parties (e.g., viaan App store).

FIG. 160 shows a diagram highlighting differences between reconfiguringa single terminal device 16002 compared to reconfiguring a small cell16004 in some aspects.

For the single terminal device 16002, there is typically only one userconfiguring his/her terminal device according to his/her needs, e.g.,there is a “One-to-One” relationship.

For the small cell 16004, there is typically one small cell serving aplurality of users which have typically different (and, in some cases,opposite) interests. A small cell configuration is thus typically atrade-off which serves the interests of all connected users in the moreappropriate possible way. Theoretically, if an unlimited number ofreconfiguration resources would be available, all requirements could bemet. In practice, however, those resources (such as computationalresources, memory resources, etc.) are limited and a reasonable share,e.g., weighing mechanism, must be applied. In contrast to the singleterminal device 16002 example, for a small cell, there is a“One-to-Many” relationship.

FIG. 161 shows an exemplary small cell architecture 16100 according tosome aspects.

The small cell 16100 may be configured to be personalized so that it mayadd specific capabilities and/or functions. The small cell 16100includes fixed, hardwired (ASIC type) functionalities 16102, which mayinclude, for example, signal processing components for one or more RATs,e.g., LTE. Small cell 16100 also includes software reconfigurableresources 16104 and memory resources 16106 configured to provide userswith the ability to modify the small cell's application layer and/orradio functions specific to their needs.

FIG. 162 shows an exemplary overall system architecture 16200 forproviding updates to the small cell according to some aspects.

A Radio Apps source code database containing source code for the radioAPPs may be provided to a front-end compiler which compiles the sourcecode Apps either from the Radio Apps source code database or the RadioLibrary. These apps are compiled in the native object code of at leastone processing element of the small cell. The configcode of the compiledApps may be tested on a shadow radio platform prior to being combinedwith other Apps in the Radio Programming Interface to form a Radio Appspackage, which is then made available to the small cell via the RadioApps Store.

The Small Cell Resources and Execution Environment may include a UnifiedRadio Application Interface including one or more of the Radio Appsconfigcodes. It may further include: an RVM computing platformconfigured to receive the configcodes from the Radio Apps store; a RadioLibrary configured to store the source code for the Radio Apps; and abackend compiler. Accordingly, the source code is compiled into programsin the native object code of a processing element the RVM computingplatform by the backend compiler. The object code programs provided bythe backend compiler may be stored in the Radio Library for use by oneof the hardware (HW) radio platform processors to implement a substitutecomponent for one or more of the existing components of the RF part.

The small cell may include software reconfigurable resources (e.g.,FPGAs, DSPs, etc.) accessible to the radio processing component (as wellas to other components, such as a baseband modem) and be able to usethese resources in order to modify radio functionality of the smallcell, e.g., to improve latency, throughput, etc. Specific resources maybe limited to specific OSI layers (such as physical layer, MAC layer,Application layer, etc.) or they may be available to any layer as apool. Different terminal devices with different radio frequency (RF)capabilities (e.g., LTE, LTE+WiFi, Bluetooth, etc.) may camp on thesmall cell at any given time, and the small cell may be configured todetect these different RF capabilities (e.g., “Information” in MSCabove), and download the most suitable package to provide to its users.In some aspects, the small cell may be configured to analyze thecalculation capabilities of its coverage in order to request/download anappropriate package from the network. The small cell may balance thecalculation power allocated to a certain radio standard (e.g., LTE) withrespect to the user(s) requirements. For example, if one or more usersasks for super-loading on LTE, the small cell may be configured toallocate more of its signaling resources to LTE.

In some aspects, the small cell may dynamically adapt its RFcapabilities to its users. For example, the small cell may provideextensions to radio protocol standards in the form of non-standard,proprietary extensions, e.g., new channel coding schemes, turbo coding,etc. In another example, for a small cell in a vehicle, the small cellmay be configured to detect a new communication standard if the vehicleenters into a new area (e.g., a foreign country, an area served bycurrently unsupported RAT, or the like), and download the appropriatesoftware in order to modify its radio functionalities to meet the newcommunication standard.

The radio layer of the small cell, may therefore, have a highly flexiblemanner of implementing new functionalities. Initially, the small cell'sradio layer processing capabilities may not be fully realized so thatthe small cell may first receive information/requests from its users inorder to install and modify its RF capabilities specific to its users.The small cell may use discontinuous reception cycles (DRX) and offloadApp layer processing in the order to modify the lower levels of itsRadio layers.

FIG. 163 shows an exemplary small cell priority determiner 16300 in someaspects of this disclosure.

Because a small cell has limited storage/computation power, anddifferent users may have different preferences, the small cell may beconfigured with a priority determiner 16300 in order to determine whichsoftware to install from the number of user requests. Initially, thesmall cell may have sufficient resources to satisfy all requests, andtherefore, the priority determiner 16300 may initially not be needed.

However, as resources become depleted, the small cell is configured toimplement a prioritization scheme to ensure that higher prioritysoftware is downloaded and installed over lower priority software. Insome aspects, the small cell may be configured with a priority assignor16302 to assign priority levels to its users. These priority levels maybe based on a user's frequency of use of the small cell, user rankingbased on user importance, etc. In some aspects, the type of softwarerequests may also be assigned a priority in order to prioritize softwareof higher importance. For example, related to vehicular communicationdevice scenarios, higher priority may be assigned to software whichprovides for better communications at high speeds when the vehicle is ona highway. Or, requests related to safety features may be prioritizedover requests related to gaming, for example. In another aspect, thepriority assignor 16302 may be configured to assign a higher priority torepeat requests from multiple users. In sum, the priority assignor 16302is configured to receive user requests and assign each request arespective priority level (e.g., based on weighing factors). Thepriority determiner 16300 may further include a priority sorter 16304configured to sort the requests according to their assigned priority.The priority sorter 16304 may further be configured to compare therequests against already installed software wherein the software of therequests can replace the already installed software. For example, if arequest for a newer version of an already installed feature is received,the small cell may delete the older version and install the newerversion in its place. The priority determiner 16300 may further includea submitter 16306 configured to submit the approved, higher priorityrequests for downloading the related software/applications/radiofunctions from an Application Store via the network.

In some aspects, the small cells may be configured with a resourcerecycler. The resource recycler may be configured to identify lesserused software/applications/radio functions installed on the softwarereconfigurable resources and uninstall them in order to free resourcesfor software of newly received requests.

FIG. 164 is an exemplary MSC 16400 describing a signaling process for asmall cell network in some aspects of this disclosure.

One or more users (e.g., terminal devices) may either submit a requestfor a particular resource/service, or, the small cell may obtain usercriteria from information received from the user or by monitoring theuser behavior. After receiving the requests and/or determining theinformation from an obtained user criteria, the small cell mayprioritize the requests as described with respect to FIG. 163 . However,if the small cell has sufficient resources to handle all of therequests, the prioritization may not be needed, and all of the requestsmay be transmitted to the network. Upon receiving the requests, thenetwork may identify the appropriate application/software in its RadioApp library and transmit the necessary executable code to the smallcell. The small cell then downloads the information received from thenetwork in order to install the functionalities from the user request(s)forwarded to the network. This may include applications and/or radiofunctionalities to install a new feature and/or update/modify anexisting feature. The small cell may be configured to relay at least aportion of this information to a user, so that the user may alsodownload the necessary software code for executing the desiredapplication/functionality. Accordingly, the small cell may be configuredto execute the new functionality entirely on its own, or with splitexecution with the user and/or network.

In some aspects, the downloaded software/application/radio function maybe distributed between the terminal device, the small cell, and/or thecloud. This split application may be partially executed on each of thesmall cell and the terminal device, or other network components. Forexample, if there is communication with a Mobile Edge Computing (MEC)node and/or a Road Side Unit (RSU), certain features of the requesteddownload could be split among the different network elements, e.g., partof the application functionality is installed in the MEC/RSU, part onthe small cell, part on a terminal device, and/or part is installed onthe core network.

In some aspects, the request to install new software/applications/radiofunctions may come from someone other than the user. For example, if oneor more users are part of a user subscription service, a serviceprovider may trigger the installation. The core network, therefore, mustbe able to identify which small cell the user is connected to so that itcan perform the software upgrade to the correct small cell.

Other examples for small cell software modifications may includesoftware that better integrates the small cell into a cloudinfrastructure in order to off-load operations to the cloud, e.g.,message redistribution tasks; new security features such as advancedencryption; and maintenance features to correct detectedvulnerabilities.

In some aspects, the small cell is configured to distinguish betweendata that is intended for the network (e.g., in formal communications)and the type of data that is intendent for a local cloud, e.g., datathat is relevant to newly installed applications. The small cell mayinclude pact filters that allow the small cell to identify thedestination of a data (e.g., similar to Traffic Flow Templates (TFTs)).These filters may be configurable, so that the appropriate filter isenabled when a certain application is enabled in the small cell, e.g.,using a particular packet filter to find game data when a gamingapplication is active. The small cell may be configured to identifywhich applications are active in order to activate the appropriatefilters.

In some aspects, the small cells may be fitted with additional hardwareto support the handling of new functions. For example, the small cellmay be fitted with a modular addition for memory or a modular front end(e.g., including FPGAs, DSPs, etc.) for signal processing.

FIG. 165 shows an exemplary flowchart 16500 describing a method forconfiguring a network access node in some aspects. The network accessnode may be a small cell network access node.

The method may include receiving a plurality of download requests fromone or more users 16502; assigning a priority to each of the downloadrequests 16504; sorting the download requests based on their assignedpriorities 16506; submitting one or more download requests to thenetwork based on the sorting 16508; receiving executable code from thenetwork in response to the one or more download requests 16510; anddownloading the executable code on a non-transitory computer-readablemedia of the network access node and reconfiguring the network accessnode based on the downloaded executable code 16512.

Small Cell Hierarchy for V2X, Mobile Vs Static Small Cells

In a V2X environment, a terminal device, e.g., a vehicular communicationdevice, may be connected to a plurality of different types of othernodes, such as mobile edge computing (MEC), RSUs, small cell networkaccess nodes (both mobile and stationary), and a macro cell networkaccess node. The number of nodes, and the type of node, that a terminaldevice is connected to, however, may be constantly changing due to aconstantly evolving environment. Accordingly, nodes which at one pointwere readily available for handling communications, e.g., handingdistributed processing, message distribution tasks, may no longer beviable candidates for such communications. Or, a change in the vehicularcommunication devices environment may have introduced a new node whichmay be better equipped for such communications.

In some aspects of this disclosure, terminal devices are configured toreceive and/or create a hierarchy of nodes differentiating between anode's mobility, coverage area, and processing capabilities.

FIG. 166 shows an exemplary V2X network environment 16600 in someaspects.

Vehicular communication device 16604 may be traveling in the samedirection as vehicular communication devices 16602 and 16606. In someaspects, vehicular communication devices 16604 may be configured to forma vehicle cluster 16610 in order to collaboratively handle certaintasks. The vehicular communication devices of cluster 16610 maycoordinate to manage access to channel resources that can be sharedbetween multiple vehicular radio communication technologies, such asDSRC, LTE V2V/V2X, and any other vehicular radio communicationtechnologies. The vehicular communication devices of a cluster maycoordinate with one another via exchange of cluster signaling. As usedherein, a cluster of devices may be any logical association of deviceswhich devices can join, generate, leave, or terminate, and exchange dataspecific to the cluster with each other. One of the vehicles withincluster 16610 may assume the role of cluster head, and be configured toinitiate the cluster and management of cluster resources.

Alternatively, the formation of the cluster 16610 may not be required.In some aspects, vehicular communication device 16604 may be configuredto detect other nodes, e.g., vehicular communication devices 16602 and16606, with a similar movement pattern to the vehicular communicationdevice's 16604 own movement, e.g., the distance between the devicesremains substantially constant. This may be achieved by signalingincluding positioning data (e.g., GNSS) between the devices, velocitydata, Doppler Shift detection, etc. Accordingly, the vehicularcommunication device 16604 may be configured to communicate withvehicular communication devices 16602 and 16606 at a different levelthan other nodes, e.g., 16660-16665, 16620, 16630.

Other vehicular communication devices 16620 and 16630 may be withinrange of vehicular communication device 16604, but, compared tovehicular communication devices 16602 and 16606, the duration of timefor which vehicular communication device 16604 may communicate withvehicular communication devices 16620 and 16630 is much shorter.Additionally, infrastructure elements 16660 and 16665 may be withinrange of vehicular communication device 16604. These otherinfrastructure elements 16660 and 16665 may be any one of fixed networkinfrastructure elements, e.g., RSU, a fixed small cell network accessnode, traffic lights, etc. Vehicular communication device 16604 may alsofall within range of macro cell network access node 16650, which mayprovide network access and/or offload processing capabilities forvehicular communication device 16604 over a wide area than other nodes,albeit at some cost.

In some aspects, terminal devices (e.g., vehicular communicationdevices) are configured to adapt in this evolving environment byimplementing a hierarchal setup to account for mobility to satisfylatency and coverage requirements. Furthermore, the terminal devices maybe configured to modify the hierarchal setup in real-time. For example,mobile edge computing (MEC) nodes, e.g., which may be installed directlyon other vehicular communication devices; mobile small cells, e.g., alsoin vehicular communication devices; static small cells, e.g., via RSUs,small cell network access nodes; and the broader cell network (e.g., viamacro cells) may be included in the hierarchy.

In some aspects, nodes determined to be “mobile” may be included at theone level of the hierarchy, and nodes determined to be “static” may beat another level at the hierarchy, and the core mobile network may be atanother level. Nodes may include a wide variety of Access Points (APs),such as small cells, MECs, RSUs, other terminal devices such as UEs orvehicular communication devices, etc.

Furthermore, the term static and mobile may be used relative to a fixedpoint (e.g., mobile meaning anything in motion, static meaning at fixedpositions). In other aspects, it may be used to describe movementrelative to the terminal device.

FIG. 167 shows a diagram 16700 describing an exemplary hierarchicalsetup in some aspects. FIG. 168A shows an exemplary internalconfiguration for a hierarchy determiner 16804 of a terminal device insome aspects. Hierarchy determiner 16804 may be included in a basebandmodem (e.g., corresponding 206 in FIG. 2 ) or a radio communicationarrangement (e.g., corresponding to 504 in FIG. 5 ) of a terminaldevice.

Hierarchy determiner 16804 may include a node detector 16812 configuredto detect other nodes within its communication range and distinguishbetween different types of nodes based on several factors. These factorsmay include a mobility factor, coverage factor, and a processingcapability factor. The mobility factor may include information ofanother node's movement pattern. In this manner, the terminal devicewould be able to distinguish between mobile nodes and static nodes. Forexample, a mobile node (e.g., a vehicular communication device) maytransmit information including velocity information and/or locationinformation, which the terminal device may use to classify it as amobile node. Also, the terminal device may detect another node'smobility based on a speed estimation performed relative to the othernode's transmitter.

Hierarchy determiner 16804 may include with a node detector 16812 whichmay be operatively coupled to an antenna 16802 (which may correspond toantenna 202 or antenna system 506 in FIGS. 2 and 5 , respectively) andbe configured to detect other nodes within the terminal device's 16800communication range. Node detector

Furthermore, hierarchy determiner 16804 may include a hierarchy sorter16814 configured to distinguish mobile nodes into mobile nodes with adifferent movement pattern and mobile nodes with a similar movementpattern. Mobile nodes with a similar movement pattern, e.g., vehiclestraveling in the same direction as the terminal device, may be detectedby the node detector 16812 based on their relative velocity to theterminal device and/or location information. The hierarchy sorter 16814may determine that another node (e.g., vehicle) has a similar movementpattern based on a history of signaling with the other node, e.g., Rxsignal strength remains constant for a certain duration of time.

In some aspects, vehicles within a same cluster are identified as havinga similar movement pattern to that of the terminal device. Vehiclestraveling in a different direction, for example, are identified ashaving a different movement pattern.

If the terminal device is in motion, therefore, the mobile nodes may bedistinguished to be relative to the terminal device's movement (e.g.,mobile nodes traveling in the same direction as the terminal device,which may include traveling in a same cluster) and classified by thehierarchy sorter 16814 accordingly.

Static nodes are those nodes whose position is fixed, e.g.,infrastructure such as RSUs, fixed small cell network access nodes,longer range base stations, etc. These types of nodes may be furtherclassified into two categories: long range and short range. Long rangenodes may include macro cell base stations, for example, while shortrange nodes may include RSU, for example.

In some aspects, once the hierarchy 16700 is assembled by the hierarchysorter 16814, the task/message distributor 16816 is configured tointeract with a node at a certain level of the hierarchy 16700 in orderto distribute processing tasks, message distribution tasks, or the like,depending on latency, coverage, and/or processing requirements. Forexample, the hierarchy determiner 16804 may be configured to interactwith the lowest level of hierarchy 16700, including, for example,interacting with mobile nodes first. The task/message distributor 16816may be configured to first distribute tasks to mobile nodes with asimilar movement pattern. However, if communications using this level ofthe hierarchy is not possible (e.g., relative mobility between twovehicles abruptly increases, data processing requirements not met,etc.), the hierarchy determiner 16804 may be configured to use anotherlevel of the hierarchy 16700 in order to secure a more stable link, butperhaps at some cost, e.g., reduced capacity. In another example, thetask/message distributor 16816 may distribute a message immediately to along range static node of the hierarchy if a coverage requirement forthe task demands maximum coverage for the message.

The terminal device 16800 may be a vehicular communication device movingat high speeds on a highway. This terminal device may be caravanningwith several other terminal devices (e.g., vehicles). The task/messagedistributor 16814 may attempt to initially distribute processing and/ormessaging tasks with a mobile node (e.g., other vehicle with a similarmovement pattern) based on the hierarchy 16700 assembled by thehierarchy sorter 16814, but if it is unable to, it may then attempt toperform the task using a static node of the hierarchy 16700 assembled bythe hierarchy sorter 16814. However, resorting to the use of the staticnode may come at a cost, e.g., additional signal processing due tochanging channel conditions, e.g., increased Doppler Effect.

In some aspects, depending on certain requirements, e.g., throughput,latency, or the like, the hierarchy determiner 16804 may be configuredto bypass the hierarchy assembled by the hierarchy sorter 16814. Forexample, if a particular communication is latency critical and needs tobe communicated immediately to the core network, the hierarchydeterminer 16804 can go directly to the core network level of thehierarchy 16700 in order to help avoid potential latency losses incommunicating between the different hierarchy levels. In anotherexample, if there is low latency between closely located vehicles, thelowest level of latency may be obtained by communicating with a node ofa lower hierarchy (e.g., a vehicular communication device configured asan MEC node and with a similar movement pattern) if in close geographicproximity.

Furthermore, the hierarchy sorter 16814 may be configured to assemblethe hierarchy 16700 based on the processing capabilities of the othernodes. For example, if there are multiple nodes with a similar movementpattern (e.g., other vehicles moving in the same direction in a trafficjam), the hierarchy sorter 16814 may be configured to include thisprocessing information in the hierarchy and the task/message distributor16816 may be configured to distribute processing and message tasks basedon this processing information, e.g., one node may have higherprocessing capabilities at a particular time than another node.

In some aspects, nodes may be added and/or removed from the hierarchy16700. Long range cell nodes can be considered to be static andavailable most of the time, but short range nodes could come and go froma terminal device's communication range, e.g., an RSU. Mobile nodes,e.g., vehicular communication devices, may be moving in oppositedirections, or they may change their movement patterns relative to theterminal device 16800. The node detector 16812 detects these changes inthe terminal device's environment, and forwards this information to thehierarchy sorter 16814, which modifies the hierarchy 16700 accordingly.For example, the dynamic management and modification of the hierarchy16700 may be altered due to a change in environment, e.g., high trafficscenario, where the movement of the terminal device 16800 is greatlyreduced.

The hierarchy determiner 16804 may determine the hierarchy 16700 in anumber of different options. In a first option, a network maycommunicate a hierarchy to the terminal device 16800. The hierarchysorter 16814 may then modify the hierarchy, especially with regards tonodes detected by the node detector 16812, e.g., the mobile nodes asthey come into and out of the terminal device's range, e.g., othervehicles. The hierarchy determiner 16804 may estimate the speed relativeto other nodes' transmitters with the node detector 16812, and thehierarchy sorter 16814 may add each respective node to either the mobileor static node level of the hierarchy accordingly.

In another aspect, the hierarchy determiner 16804 may be configured todetermine the hierarchy in a distributed manner with other devices,e.g., mobile nodes with similar movement patterns. In V2X broadcastingcommunications, each terminal device may decode signals from multiplenode transmitters, and be configured to add each node based on itsrelative movement, e.g., there is no need for coordination from acentralized controller. The hierarchy determiner 16804 mayassemble/modify the hierarchy tree itself (or modify one received froman outside source) by detecting nodes in its surroundings.

In some aspects, terminal devices in the V2X environment, such as thosein a cluster of vehicles or mobile nodes which have been determined tohave a similar movement pattern, may be able to handle the determinationof the hierarchies collaboratively. Accordingly, the tasks related tothe assembly and/modification of the hierarchy for a particular clusterof vehicles may be distributed across all vehicles of the cluster.

In some aspects, different predetermined hierarchies may be arranged ona geographic grid which may be communicated to the terminal device 16800as it passes through a particular area. For example, if a terminaldevice has a programmed route which it will follow (e.g., using avehicle's GPS navigation system), the hierarchy determiner 16804 mayreceive an “initial” hierarchy to use at each of a plurality of pointsalong the route, which may include information for the static node levelof the hierarchy, e.g., a list including the core network and staticinfrastructure elements (e.g., RSUs, static small cell stations, etc.),and the hierarchy sorter 16814 may be configured to add nodes detectedby the node detector 16812 to the “mobile node” level accordingly.

In another exemplary option, terminal devices may communicatehierarchies between themselves. For example, for vehicular communicationdevices traveling in opposite directions, each vehicular communicationdevice may communicate a hierarchy to the other as they pass each other,since one vehicular communication device's past location will become thepassing vehicular communication device's future location. Accordingly,the vehicular communication devices may share knowledge ofinfrastructure elements with other vehicular communication devices goingtowards that direction. Each vehicular communication device may still beable to modify the hierarchy, including at the mobile node level, e.g.,other mobile nodes with similar movement patterns that the passingvehicle would not have information about.

FIG. 168B shows an exemplary MSC 16850 describing a method foridentifying capabilities of one or more small cells for determining asmall cell hierarchy in some aspects.

The terminal device may query one or more small cells for each of theirrespective capabilities, i.e. 16852 to Small cell #1 through 16854 toSmall Cell #N (where N is an integer greater than 1), after detectingthe one or more small cells (e.g., via the Node Detector). A terminaldevice may submit this query about a small cell's correspondingcapabilities while it is attached to a small cell or prior to attachingto a small cell.

Each of the respective small cells may then reply to the query byproviding their capabilities 16856 and 16858. Each of these may includea “capabilities identifier,” wherein the “capability identifier” foreach small cell may include at least one of the following: latency ofthe small cell for information processing, coverage area of the smallcell, service capabilities of the small cell (e.g. interoperabilityservices providing translation capabilities between IEEE 802.11p basedDSRC and LTE C-V2X services), access conditions of the small cell (e.g.open access (for all), access restricted to specific user groups), amobility factor of the small cell (e.g. fixed small cell or mobile smallcell, magnitude of mobility, etc.). Small cells #1 and #N may beorganized on a single hierarchy level or on different hierarchy levels.

When a service is requested from a small cell (e.g. simpleredistribution of messages, interoperability services such astranslating messages from IEEE 802.11p based DSRC to LTE C-V2X and viceversa, or the like), a “budget identifier” may be attached to themessage. If this “budget identifier” is attached to the message, it mayinclude information such as the latency budget, the transmission powerbudget, and/or information security requirements.

The latency budget may include information indicating how muchprocessing time is available for the infrastructure/network to executethe task. For example, this may include how much processing time isavailable to execute interoperability services such as translatingmessages between two communication protocols, e.g. from IEEE 802.11pbased DSRC and LTE C-V2X. The latency budget typically includes theoverall processing and information management/forwarding time across allelements of the small cell hierarchy.

The transmission budget may include information indicating how muchoutput power should be available in the small cell (or other networkaccess node/infrastructure element) to redistribute the message. Thisrequirement may also be expressed as a minimum and/or a maximum coveragearea.

The information security requirements may include information indicatingthe requirements that need to be met in the processing ofdata/signals/information. For example, there may be legal standards incertain countries, or some information elements (e.g. identifyingspecific users and/or vehicles, etc.) may only be processed within aspecific geographic range of the users (i.e. data must be processed inthe immediate proximity of the user and may not be forwarded to a remoteserver for further processing).

The terminal device, i.e. through the hierarchy determiner 16804, may beconfigured to follow the corresponding budget and other requirements inorder to choose (i.e. distribute the messages and/or tasks) between thesmall cells, infrastructure elements, and the network in the hierarchybased on the received capabilities and its requirements 16860.

FIG. 168C shows an exemplary diagram describing a process for meetinglatency requirements in some aspects. It is appreciated that FIG. 168Cis exemplary in nature and may thus be simplified for purposes of thisexplanation.

Following the requirements/information of the identified “capabilityidentifier” and/or “budget identifier,” the processing through the smallcell/infrastructure element/core network hierarchy may be chosen.

In FIG. 168C, a high power small cell may need to be identified in orderto provide a specific service, e.g. interoperability services such astranslating messages from IEEE 802.11p based DSRC to LTE-C2V or viceversa. In the scheme shown on the left (for device 16862), the latencybudget requirements are not met since the processing/management of datathrough the complex hierarchy takes too much time. However, in thescheme shown on the right (for device 16864), the latency budgetrequirements are met, and the processing and management of data thoughthe complex hierarchy is performed in an acceptable amount of time. Theprocessing paths throughout the hierarchy are shown as 16866 and 16868for terminal devices 16862 and 16864, respectively.

By identifying the “capability identifier” of each of the small cellsand by attaching a “budget identifier” to its message, the terminaldevice on the right (i.e. vehicular communication device of 16864) isable to implement a hierarchy which provides the necessary processingrequirements in order to perform a task within a suitable amount oftime.

Furthermore, as shown in FIG. 168C, a single small cell may receive arequest and provide the answer to the user (as shown for 16862) or onesmall cell may receive a request and a different small cell may providethe answer (as shown in 16864). The approach taken in 16864 may providethe additional benefit of being able to operate in a method similar to aFull Duplex operation, e.g. while the first small cell is stillreceiving data, the available parts of the frame are immediatelyprocessed and the answer is immediately provided to the user. In thismanner, while the user is sending data to the first small cell, thesecond small cell may begin to transmit data in response to the usersubmitted data following a short processing delay. This principle isfurther detailed in FIG. 168D.

By transmitting and receiving signals from two different small cells,16874 and 16876, respectively, the terminal device 16872 (which maycorrespond to device 16864 in FIG. 168C) may more evenly distribute theprocessing of the data across the small cells so that the processingdelay 16888 is shortened. The receiving small cell 16874 may receive theincoming frame 16878 indicating data to be processed by the small cells,and immediately begin the processing/distribution of the processing ofthe data. The transmitting small cell 16876 may begin to transmit theoutgoing frame 16880 immediately back to the terminal device 16872following a short processing delay 16888 while the remaining data isstill being processed. In some aspects, in order to simplify the userreceiver requirements (in this case, a vehicular communication device)since simultaneous transmission and reception is a technologicallychallenging risk (due to interference issues), the terminal device 16872is able to exploit the different locations of the small cells. This mayresult in different path angles at which the communications are beingtransmitted and received, and these different path angles may be used tomitigate interference. The terminal device 16872 may be configured toemploy a respective antenna beamforming for the transmit path and adifferent antenna beamforming for the receive path, such as to providesufficient signal diversification between the two paths.

16882 shows the times during which the terminal device is onlytransmitting data, 16884 shows the time during which the terminal deviceis transmitting and receiving data simultaneously, and 16886 shows thetime during which the terminal device is only receiving data.

FIG. 169 shows a flowchart 16900 describing a method for creating ahierarchy of nodes to use in wireless communications in some aspects.

The method of flowchart 16900 may include detecting a plurality of nodes16902; determining at least one of a mobility factor, coverage areafactor, or a processing capability factor, for each node of theplurality of nodes 16904; sorting the plurality of nodes into ahierarchy based on its at least one determined factor 16906; andcommunicating with at least a first node of the plurality of nodes basedon the hierarchy 16908.

Dynamic Selection of Compression Modes

Terminal devices may transmit and receive data streams that includeuser-plane data. FIG. 170 shows a basic example according to someaspects, where terminal device 17002 may transmit or receive a datastream with server 17006 via a radio access channel provided by networkaccess node 17004. In the uplink direction, terminal device 17002 maygenerate the data stream (e.g., on the user-plane in application orbaseband layers), and may transmit the data stream to network accessnode 17004 in the form of wireless signals over a radio access channel.Network access node 17004 may receive the wireless signals andsubsequently send the data stream to server 17006, which may act as theendpoint of the data stream (e.g., the end of a software-level signalingconnection between terminal device 17002 and server 17006). Server 17006can be located in any network location, such as at network access node17004 (e.g., part of network access node 17004), in an edge network nextto network access node 17004 (e.g., in an edge computing server, such asa MEC server, that interfaces with network access node 17004), in thecore network behind network access node 17004, or in an externalinternet network to which the core network connects. In the downlinkdirection, server 17006 may generate the data stream and send the datastream to network access node 17004. Network access node 17004 may thentransmit the data stream in the form of wireless signals to terminaldevice 17002 over the radio access connection. Terminal device 17002 mayreceive and process the wireless signals to obtain the data stream.

Terminal device 17002 and server 17006 may therefore use asoftware-level signaling connection to transfer the data stream in thedownlink and/or uplink direction, where the software-level signalingconnection may use the radio access channel (between terminal device17002 and network access node 17004) for wireless transport at thephysical layer. However, the ability of the radio access channel totransport the data stream (in the form of wireless signals afterprocessing, RF mixing, amplification, and wireless transmission) maydepend on its channel strength. For example, stronger radio accesschannels (e.g., having higher SNR) may be able to support higher datarates than weaker radio access channels (e.g., having lower SNR).Accordingly, if the radio access channel is weak it may not be able tosupport a high data rate. Depending on the strength of the radio accesschannel (e.g., characterized by its SNR or other channel metric),terminal device 17002 and server 17006 may thus use data compression totransfer the data stream. For example, terminal device 17002 and server17006 may compress the data stream according to a compression format(e.g., an audio compression format such as MP3, a video compressionformat, or any other type of compression format) and transfer the datastream in the compression format (e.g., a compressed data stream thatincludes the data stream after it has been compressed with thecompression format). As the compressed data stream is condensed comparedto the uncompressed data stream, it can be transferred over the radioaccess channel with a lower data rate.

Issues with data rate can also be related to spectrum bandwidth. Forexample, radio access channels with higher bandwidth (e.g., allocatedmore frequency resources/spectrum) may be able to support higher datarates than others. Accordingly, if the radio access channel has lowerbandwidth, terminal device 17002 and server 17006 may compress the datastream with a compression format (thus condensing the size of the datastream) and then transfer the compressed data stream at a lower datarate over the radio access channel. Compression can also help with datastorage, as compressed data may be condensed in size compared touncompressed data. The compressed data will therefore take up lessstorage space when stored in a memory.

While the use of compression may assist terminal device 17002 and server17006 in transferring the data stream when the data rate of the radioaccess channel is limited, compression may also present some drawbacks,especially in dynamic (realtime) application where data is exchangedbetween terminal device 17002 and server 17006 in realtime. For example,the processing involved in compression and decompression may lead tohigher power usage. For example, terminal device 17002 may use a digitalprocessor (e.g., a baseband or application processor, depending on whichlayer the compression/decompression is performed) to compress anddecompress the data stream. In an example where terminal device 17002 istransmitting the data stream in a compression format, the digitalprocessor of terminal device 17002 may perform compression processing onthe data stream to apply the compression format to the data stream. Thiscompression processing may consume power at the digital processor, thuscausing battery drain at terminal device 17002. This can likewise holdin the downlink direction, where server 17006 may send the data streamto terminal device 17002 in a compression format. The digital processorof terminal device 17002 may perform decompression processing on thedata stream to revert the compression format (and obtain the data streamin its initial format). This decompression processing may similarlyconsume power at the digital processor and lead to battery drain.

In addition to power usage, compression and decompression processing mayalso introduce latency. For example, when terminal device 17002 receivesthe data stream in a compression format, its digital processor may firstperform decompression processing on the data stream before terminaldevice 17002 can actually use the data stream (e.g., process and reactto the information in the data stream, such as for an application-layerusage). This may introduce processing latency, as terminal device 17002may not be able to use the data stream until the decompressionprocessing is complete. These issues with latency can also be seen atserver 17006, as it may likewise perform decompression processing on thedata stream (after receiving the data stream from terminal device 17002)before it can use the information in the data stream. Thiscompression-related latency can be particularly problematic inlatency-sensitive applications, such as autonomous driving or factoryrobot control, which may have low latency tolerance as the informationin the data stream is immediately used (e.g., to avoid collisions ormanage an assembly line).

Accordingly, various aspects of this disclosure provide a dynamiccompression format selection system with spectrum offload. For example,in some aspects, a terminal device may initially be transmitting orreceiving a data stream in a first compression format on primaryspectrum. The terminal device may then identify secondary spectrum anduse both the primary and secondary spectrum to transfer the data streamin a second compression format with reduced latency and/or powerconsumption than the first compression format. Even if the secondcompression format increases the data rate demands of the data stream(e.g., if it has lower compression efficiency than the first compressionformat), the introduction of the secondary spectrum may provide enoughextra bandwidth for the terminal device to meet the increased data ratedemands. This can apply for cases where the second compression formatinvolves is a compressed compression format and where the secondcompression format is an uncompressed compression format (e.g., wherethe data stream is transferred in its uncompressed form). As the secondcompression format has lower power usage (e.g., at the digitalprocessors involved in compression/decompression) and/or processinglatency than the first compression format, the terminal device may beable to reduce its power usage and/or reduce latency in the data stream.This can be particular true for cases where the second compressionformat is an uncompressed compression format, as the terminal device maybe able to avoid performing any compression/decompression processing forthe data stream, thus leading to large reduction in power saving andlatency.

FIG. 171 shows an exemplary internal configuration of terminal device17100 according to some aspects. As shown in FIG. 171 , terminal device17100 may include controller 17102, stream application 17104, digitalcompression processor 17106, router 17108, transceivers 17110 and 17112,and antennas 17114 and 17116 (e.g., single antennas or antenna arraysfor beamforming or MIMO). The following description provides anintroduction for each of these components, followed by a detaileddescription of their operation. With initial reference to controller17102, controller 17102 may be a processor (e.g., a special-purposeprocessor) configured to control selection of a compression format for adata stream. Controller 17102 may therefore be configured with controllogic (e.g., in the form of executable instructions) that definesdetection of triggering conditions, selection of compression formats,and control of data stream routing as described below.

Stream application 17104 may be an application that generates and/orreceives the data stream. For example, in an uplink case, streamapplication 17104 may generate the data stream as an uplink stream ofuser data addressed to server 17006. In a downlink case, streamapplication may receive the data stream as a downlink stream of userdata. In some aspects, stream application 17104 may be anapplication-layer application (e.g., running on an application processorof terminal device 17100) that generates or receives anapplication-layer data stream (e.g., audio, voice, video, file, realtimestreaming, gaming, or any other type of data stream). In other aspects,stream application 17104 may be a baseband-layer application (e.g.,running on a baseband modem of terminal device 17100) that generates orreceives a baseband-layer data stream, such as a voice data stream forvoice communications or a video data stream for video communications(e.g., 2D or 3D).

Digital compression processor 17106 may be a digital processorconfigured to perform compression and/or decompression processing on thedata stream. Digital compression processor 17106 can be anapplication-layer component (e.g., part of an application processor ofterminal device 17100) or a baseband component (e.g., part of a basebandmodem of terminal device 17100). In various aspects, digital compressionprocessor 17106 may be configured to only perform compression (e.g., ifthe data stream is an uplink data stream), to only perform decompression(e.g., if the data stream is a downlink data stream), or to perform bothcompression and decompression (e.g., if the data stream is abidirectional data stream). Digital compression processor 17106 may beconfigured to perform compression/decompression processing according tomultiple compression formats, such as by compressing a data stream intoa first and second compression format and/or decompressing a data streamfrom a first and second compression format. The compression format thatdigital compression processor 17106 applies or reverts may be controlledby a compression selection signal provided by controller 17102. In theuplink direction, digital compression processor 17106 may receive thedata stream from stream application 17104, compress the data stream intoa compression format, and provide the data stream (in the compressionformat) to router 17108. In the downlink direction, digital compressionprocessor 17106 may receive the data stream in a compression format fromrouter 17108, decompress the data stream out of the compression format,and provide the data stream (in an uncompressed compression format) tostream application 17004.

Router 17108 may be a processor (e.g., a special-purpose processor)configured to route the data stream between digital compressionprocessor 17106 and transceivers 17110 and 17112. For example, in theuplink direction, router 17108 may receive the data stream (in acompression format) from digital compression processor 17106, and mayroute the data stream to one or both of transceivers 17110 and 17112depending on a routing selection signal provide by controller 17102. Insome aspects where router 17108 routes the data stream to transceivers17110 and 17112, e.g., in the uplink direction, router 17108 may splitthe data stream (in the compression format) into first and second parts.Router 17108 may then route the first part to transceiver 17110 and thesecond part to transceiver 17112. In the downlink direction, router17108 may be configured to receive first and second parts of the datastream, recombine the first and second parts, and provide the datastream to digital compression processor 17106. In some aspects, router17108 may also perform baseband modem processing functions (e.g.,protocol stack and physical layer functions), such as to apply basebandprocessing on the data stream (in the compression format) to prepare thedata stream for transmission by transceivers 17110 and 17112, and toreceive the data stream from transceivers 17110 and 17112 and revertcounterpart baseband processing applied to the data stream by the radioaccess network. Router 17108 can therefore represent the baseband layersof terminal device 17100.

Transceivers 17110 and 17112 may be RF transceivers and/or mmWavetransceivers with mmWave Front End modules configured in the manner ofRF transceiver 204 of terminal device 102 in FIG. 2 . Antennas 17114 and17116 may be antennas configured in the manner of antenna system 202 ofterminal device 102 in FIG. 2 (e.g., a single antenna or a beamformingarray, such as for a mmWave system operating, for example, above 23GHz). Transceiver 17110 may be configured to, in the uplink direction,convert digital data (received from router 17108, e.g., digital data inthe data stream) into analog RF signals and to wirelessly transmit theanalog RF signals via antenna 17114. Transceiver 17110 may be configuredto, in the downlink direction, wirelessly receive analog RF signals viaantenna 17114 and to convert the analog RF signals into digital data forrouter 17108. Similarly, transceiver 17112 may be configured to, in theuplink direction, convert digital data (received from router 17108,e.g., digital data in the data stream) into analog RF signals and towirelessly transmit the analog RF signals via antenna 17116. Transceiver17112 may be configured to, in the downlink direction, wirelesslyreceive analog RF signals via antenna 17116 and to convert the analog RFsignals into digital data for router 17108. In some aspects, transceiver17110 may be designed for radio transmission and reception on firstspectrum (e.g., primary spectrum, such as a frequency band below 23 GHzor below 6 GHz), such as where transceiver 17110 includes a poweramplifier tuned for amplification of signals in the first spectrum. Insome aspects, transceiver 17112 may be designed for radio transmissionand reception on second spectrum (e.g., secondary spectrum, such as in afrequency band above 23 GHz), such as where transceiver 17112 includes apower amplifier tuned for amplification of signals in the secondspectrum.

Various aspects of dynamic compression selection will now be describedfor FIGS. 172-177 . With initial reference to FIGS. 172-173 , FIGS.172-174 show a first example of dynamic compression selection using twonetwork access nodes. As shown for scenario 17200 in FIG. 172 , terminaldevice 17100 may initially be connected with network access node 17202over a first radio access channel. Network access node 17202 mayinterface with server 17206) where server 17206 may be located withnetwork access node 17202, in an edge network next to network accessnode 17202, in a core network behind network access node 17202, or in anexternal internet network connected to the core network. Network accessnode 17204 may also interface with server 17206, and may be locatedproximate to terminal device 17100, such as operating in a frequencyband above 23 GHz with a frequency bandwidth above 100 MHz up to severalGHz bandwidth.

FIG. 173 shows message sequence chart 17300 according to some aspects,which describes a procedure for dynamic compression selection in theuplink direction in the example of FIG. 172 . Terminal device 17100 maygenerate and compress a data stream in a first compression format (C1)in stage 17302. For example, stream application 17104 may generate thedata stream as an uplink stream of user data addressed to server1720417206 (e.g., where there is a software-level signaling connectionwith endpoints at stream application 17104 and server 906). Digitalcompression processor 17106 may then apply a first compression format tothe data stream, where controller 17102 may provide a compressionselection signal to digital compression processor 17106 that specifiesthe first compression format.

Terminal device 17100 may then wirelessly transmit the data stream (inthe first compression format) on primary spectrum (S1, e.g., firstspectrum) to network access node 17202 in stage 17304 a. For example,digital compression processor 17106 may then provide the data stream (inthe first compression format) to router 17108. Controller 17102 mayprovide a routing selection signal to router 17108 that specifieswireless transmission of the data stream on the primary spectrum. Router17108 may therefore route the data stream to transceiver 17110, whichmay transmit the data stream via antenna 17114 in the form of wirelesssignals on the primary spectrum. This may wirelessly transmit the datastream to network access node 17202 over the first radio access channel.

Network access node 17202 may then wirelessly receive the wirelesssignals that include the data stream, and may process the wirelesssignals to obtain the data stream (in the first compression format).Network access node 17202 may then send the data stream to server 17206in stage 17304 b.

Server 17206 may receive the data stream and decompress the data streamto revert the first compression format. Server 17206 may thereforerecover the data stream in its initial form, thus completing transfer ofthe data stream over the software-level signaling connection betweenstream application 17104 and server 17206.

As previously introduced, the use of compression may condense the datastream, thus reducing its data rate and/or memory storage demands whenit is wirelessly transmitted over the radio access channel betweenterminal device 17100 and network access node 17202. However, this useof compression may also increase power usage at terminal device 17100 asdigital compression processor 17106 may draw battery power to performthe compression processing of stage 17302. This use of compression mayadditionally or alternatively add latency to transfer of the datastream, as there may be processing latency when digital compressionprocessor 17106 applies the first compression format to the data streamin stage 17302 and when server 17206 reverts the first compressionformat in 17306. Accordingly, when compression is used it may takeserver 17206 a longer duration of time (e.g., measured from when thestream is generated by stream application 17104) to obtain the datastream in its initial form.

This added power usage and/or latency can become problematic over time.For example, power usage at terminal device 17100 may deplete itsbattery power. In another example, the data stream may be used forlatency-sensitive uses, such as for autonomous driving, factory robotcontrol, M2M, or other applications where information is dynamicallyexchanged between terminal device 17100 and 17206 multiple times andrequires a fast response with low latency. Accordingly, if there isexcessive latency (e.g., an unacceptable duration of time passes fromthe point when the data stream is generated to when server 17206 obtainsthe data stream in its initial form), the performance of the applicationmay suffer.

Accordingly, terminal device 17100 may be configured to detect atriggering condition in stage 17308. In some aspects, the triggeringcondition can be related to a power status of terminal device 17100 or alatency parameter of the data stream. For example, as shown in FIG. 171, controller 17102 may receive control variables as input, whichcontroller 17102 may monitor and detect the triggering condition basedon. In one example, the control variables may include a power status ofterminal device 17100. The power status can be, for example, a remainingbattery power level of a battery power supply of terminal device 17100or a power-saving mode indicator. In cases where the power status is aremaining battery power level, controller 17102 may be configured tomonitor the remaining battery power level and to determine whether theremaining battery power level is below a battery power level threshold(e.g., by periodically comparing the remaining battery power level tothe predefined battery power level threshold). If controller 17102determines that the remaining battery power level is less than thebattery power level threshold, controller 17102 may detect that thetriggering condition has occurred in stage 17308. In some aspects, thebattery power level threshold may be predefined and/or fixed. In otheraspects, the battery power level threshold may be dynamic. For example,in some cases server 17206 may be configured to calculate the batterypower level threshold and send the battery power level threshold toterminal device 17100. Server 17206 may calculate this battery powerlevel threshold, for example, based on a power consumption scenario ofterminal device 17100. In one example of this, terminal device 17100 maybe performing a particular task, such as transmission and/or receptionof the data stream or an unrelated task. Server 17206 may then, withknowledge of this task, estimate the power consumption at terminaldevice 17100 to complete the task (e.g., using a power consumption modelfor terminal device 17100, which can be common across terminal devicesor can be specific to terminal device 17100, e.g., based on a userprofile of terminal device 17100). Server 17206 may then determine thebattery power level threshold based on the estimated power consumption,and send the battery power level threshold to terminal device 17100. Insome cases, server 17206 may update the battery power level thresholdover time (e.g., dynamically recalculate) and send updated battery powerlevel threshold to terminal device 17100. Controller 17102 may then usethis as the battery power level threshold to which to compare theremaining battery power level.

In cases where the power status is a power-saving mode indicator (e.g.,when a user of terminal device 17100 manually triggers a power-savingmode), controller 17102 may determine whether the power-saving modeindicator specifies that a power-saving mode is enabled. If controller17102 determines that the power-saving mode is enabled, controller 17102may detect that the triggering condition has occurred.

In another example, the control variables can additionally oralternatively include a latency parameter of the data stream. Thelatency parameter can be a measured latency, such as where server 17206measures the latency of the data stream and sends a measurement reportincluding the measured latency back to terminal device 17100 (e.g., onthe software-level signaling connection). Controller 17102 may thereforemonitor the measured latency and determine whether the measured latencyis above a predefined latency threshold (e.g., by periodically comparingthe measured latency to the predefined latency threshold). If controller17102 determines that the measured latency is greater than thepredefined latency threshold, controller 17102 may detect that thetriggering condition has occurred in stage 17308.

After detecting the triggering condition, controller 17102 may attemptto adjust transfer of the data stream to reduce power usage and/orreduce latency. In particular, controller 17102 may attempt to switch toa more power-efficient or lower-latency compression format, and tointroduce additional bandwidth that can support any resulting increasein data rate demands. This introduction of this additional bandwidth mayenable terminal device 17100 to use a compression format that has lowercompression efficiency but also lower power usage and/or latency thanthe first compression format. Accordingly, even though a higher data maybe needed to continue to transfer the data stream (e.g., if it is notcompressed to the same degree as with the first compression rate), theadded bandwidth may enable terminal device 17100 to continue tosuccessfully transfer the data stream over the radio access channel.

In the example of FIGS. 172-174 , terminal device 17100 may use a secondnetwork access node, e.g., network access node 17204, to transfer thedata stream on the secondary spectrum. This is shown in scenario 17208of FIG. 172 , where terminal device 17100 may establish a second radioaccess channel with network access node 17204 on the secondary spectrum,and use this second radio access channel to send part of the datastream.

Terminal device 17100 may therefore identify a second compression format(C2) and may identify secondary spectrum (S2, e.g., second spectrum) forthe second radio access channel in stage 17310. In some aspects, theprimary spectrum may be licensed spectrum, while the secondary spectrummay be unlicensed or shared spectrum. For example, controller 17102 mayidentify the secondary spectrum from a pool of spectrum that isavailable to terminal device 17100 for use (e.g., that terminal device17100 is permitted to use per various wireless standards, spectrumallocations by networks, and/or spectrum licensing) and that terminaldevice 17100 supports use of. For example, as previously introduced,transceiver 17112 may be configured to perform wireless transmission andreception in the secondary spectrum, and the secondary spectrum maytherefore be in the pool of spectrum from which controller 17102identifies the secondary spectrum from.

In some aspects, terminal device 17100 may first perform a cell searchto detect network access node 17204. Terminal device 17100 may thenconnect to network access node 17204 and determine the secondaryspectrum based on the spectrum available for a radio access channel withnetwork access node 17204. For example, once connected to network accessnode 17204, network access node 17204 may send terminal device 17100 aresource allocation that assigns spectrum to terminal device 17100.Terminal device 17100 may then identify some or all of this assignedspectrum as the secondary spectrum.

In some aspects, the primary spectrum may be in a first frequency bandwhile the secondary spectrum may be in a second frequency band. Forexample, the primary spectrum may be in an LTE or 5G NR licensed band,while controller 17102 may identify the secondary spectrum from theunlicensed Industry, Scientific, and Medical (ISM) band. In anotherexample, the primary spectrum may be in a licensed mmWave band (e.g.,24-34 GHz) while controller 17102 may identify the secondary spectrumfrom an unlicensed mmWave band (e.g., 57-71 GHz). In some aspects, thefirst radio access channel (with network access node 17202) on theprimary spectrum may use a different radio access technology than thesecond radio access channel (with network access node 17204) on thesecondary spectrum.

With reference to selection of the second compression format in stage17310, the second compression format may have a lower compressionefficiency than the first compression format (e.g., may not condense thedata stream and/or reduce the data rate demands of the data stream tothe same degree as the first compression format). In some aspects, thesecond compression format may have a lower power usage (e.g., by digitalcompression processor 17106) than the first compression format and/ormay have a lower latency (e.g., lower processing latency when applied tothe data stream by digital compression processor 17106) than the firstcompression format. In some aspects, the second compression format maybe an uncompressed compression format (e.g., where digital compressionprocessor 17106 does not apply compression to the data stream), while inother aspects the second compression format may be a compressedcompression format (e.g., where digital compression processor 17106applies compression to the data stream).

In some aspects, controller 17102 may select the second compressionformat based on a prescribed response for detection of the triggeringcondition. For example, controller 17102 may be configured to select thesame second compression format whenever the triggering condition isdetected in stage 17308. In some aspects, controller 17102 may beconfigured to detect a plurality of triggering conditions that are eachmatched to a prescribed compression format. For example, controller17102 may use a plurality of triggering conditions that are each definedby a different predefined threshold (e.g., a predefined remainingbattery power level or measured latency threshold). When controller17102 detects, for example, a first triggering condition of theplurality of triggering conditions in stage 17308, controller 17102 mayidentify the prescribed compression format for the first triggeringcondition as the second compression format. In this example, thetriggering conditions and second compression rates may be ordered andpaired according to their values. For example, the first triggeringcondition may use a first predefined remaining battery power levelthreshold while a second triggering dentition may use a secondpredefined remaining battery power level threshold that is lower thanthe first predefined remaining battery power level. The secondtriggering condition may therefore be paired with a prescribedcompression format that has lower power usage than the prescribedcompression format paired with the first triggering condition.Accordingly, when the remaining battery power is lower, controller 17102may be configured to select a second compression format that has lowerpower usage. Triggering conditions for measured latency can be organizedin a similar manner. For example, the first triggering condition may usea first predefined latency threshold while a second triggering dentitionmay use a second predefined latency threshold that is higher than thefirst predefined remaining battery power level. The second triggeringcondition may therefore be paired with a prescribed compression formatthat has lower latency than the prescribed compression format pairedwith the first triggering condition.

In some aspects, controller 17102 may be configured to first select thesecond compression format in stage 17310 and then identify the secondaryspectrum based on the second compression format. For example, aspreviously indicated, the second compression format may have a lowercompression efficiency than the first compression format. When terminaldevice 17100 is transmitting the data stream in the first compressionformat in stage 17304 a, the data stream may have a first data ratedemand. As the second compression format has lower compressionefficiency, the data stream in the second compression format may have asecond data rate demand that is higher than the first data rate demand(as there is more data to transfer). Controller 17102 may therefore beconfigured to determine the second data rate demand (e.g., based on thecompression efficiency of the second compression format) and to selectan amount of spectrum sufficient to meet the data rate demand as thesecondary spectrum. As terminal device 17100 may continue to use theprimary spectrum when transmitting the data stream in the secondcompression format, controller 17102 may therefore be configured toselect secondary spectrum that, when combined with the primary spectrum,has sufficient bandwidth to meet the second data rate demand (e.g., tosupport transfer of the data stream in the second compression format).In some aspects, controller 17102 may determine, based on the seconddata rate demand, a total amount of spectrum for meeting the data ratedemand, determine a difference between the total amount of spectrum andthe size of the primary spectrum, and select an amount of spectrumgreater than or equal to the difference as the secondary spectrum.

In some aspects, terminal device 17100 may exchange control signalingwith server 17206 when selecting the second compression format. Forexample, in some aspects controller 17102 may select the secondcompression format and subsequently send control signaling to server17206 (e.g., over the software-level signaling connection) thatspecifies the second compression format. Controller 17102 can send thiscontrol signaling before terminal device 17100 transmits the data streamin the second compression format or can send the control signaling withthe data stream in the second compression format (e.g., as header orother control information accompanying the data stream in the secondcompression format). Server 17206 may therefore know what compressionformat to revert when receiving the data stream. In other aspects,controller 17102 and server 17206 may exchange control signaling tonegotiate the second compression format. For example, controller 17102may send control signaling that specifies a proposed compression format.Server 17206 may respond with control signaling that accepts theproposed compression format as the second compression format or withcontrol signaling that denies the proposed compression format as thesecond compression format. Controller 17102 may then propose anothercompression format in subsequent control signaling, and according to oneaspect may continue re-proposing compression formats until server 17206accepts the proposed compression format.

After selecting the second compression format and secondary spectrum instage 17310, terminal device 17100 may begin compressing the data streamwith the second compression format and splitting the data stream (in thesecond compression format) into parts in stage 17312. For example,controller 17102 may provide a compression selection signal to digitalcompression processor 17106 that instructs digital compression processor17106 to apply the second compression format to the data stream.Controller 17102 may also provide a routing selection signal thatinstructs router 17108 to split the data stream (in the secondcompression format) into a first part and a second part, and to send thefirst part to transceiver 17110 and the second part to transceiver17112.

Digital compression processor 17106 may then apply the secondcompression format to the data stream (e.g., to the data in the datastream that stream application 17104 is currently generating). In caseswhere the second compression format is a compressed compression format,digital compression processor 17106 may perform compression on the datastream to produce the data stream in the second compression format(e.g., where the data stream is condensed in size compared to itsinitial format). In cases where the second compression format is anuncompressed compression format, digital compression processor 17106 maynot perform compression on the data stream to produce the data stream inthe second compression format, and may instead pass the data streamthrough in uncompressed form.

After applying the second compression format to the data stream (e.g.,applying a compressed or uncompressed compression format), digitalcompression processor 17106 may provide the data stream (in the secondcompression format) to router 17108. Router 17108 may then split thedata stream into a first part and a second part, and send the first partto transceiver 17110 and the second part to transceiver 17112. This maybe a continuous procedure, where router 17108 continuously separates thedata in the data stream into the first and second parts over time. Insome aspects, the first and second parts may be equal in size (e.g.,where router 17108 sends approximately the same amount of data from thedata stream to transceiver 17110 as to transceiver 17112). In someaspects, router 17108 may be configured to split the data stream intothe first and second parts according to a target separation ratio. Forexample, router 17108 may split the data stream into the first andsecond parts where the ratio between the first and second parts is equalto the target separation ratio. In another example, controller 17102 mayselect a target separation ratio, such as to optimize transmission ofthe data stream over the first and second radio access channels. Forinstance, controller 17102 may determine a target separation ratio thatreduces (e.g., optimizes) the overall streaming time including thetransmission time and compression/decompression latency time. Controller17102 can determine this target separation ratio based on available datarate and latency of the first and second radio access channels (fromterminal device 17100 to network access node 17202 and from terminaldevice 17100 to network access node 17204, respectively).

Terminal device 17100 may then wirelessly transmit the first part of thedata stream (in the second compression format) on the primary spectrumto network access node 17202 via transceiver 17110 in stage 17314 a.Terminal device 17100 may also wirelessly transmit the second part ofthe data stream (in the second compression format) on the secondaryspectrum to network access node 17204 via transceiver 17112 in stage17316 a. Accordingly, as terminal device uses both the primary andsecondary spectrum, terminal device 17100 may continue to be able totransmit the data stream even if the second compression format has lowercompression efficiency than the first compression format. Furthermore,as the second compression format has a lower power usage and/or latencythan the first compression format, terminal device 17100 may be able toreduce its power usage (e.g., for its digital processors) and/or reducethe latency of the data stream.

As shown in FIG. 173 , network access node 17202 may wirelessly receivethe first part of the data stream on the primary spectrum (on the firstradio access channel), and may then send the first part of the datastream to server 17206 in stage 17314 b. Network access node 17204 maysimilarly wirelessly receive the second part of the data stream on thesecondary spectrum (on the second radio access channel) and send thesecond part of the data stream to server 17206.

Server 17206 may receive the first and second parts of the data streamfrom network access nodes 17202 and 17204. Server 17206 may thenrecombine the first and second parts to obtain the data stream in thesecond compression format in stage 17318. Server 17206 may then revertthe second compression format to obtain the data stream in its initialformat (e.g., as generated by stream application 17104). For example, ifthe second compression format is a compressed compression format, server17206 may apply decompression processing on the data stream to revertthe second compression format. If the second compression format is anuncompressed compression format, server 17206 may not applydecompression processing on the data stream as it is already in itsinitial format.

In some aspects, network access nodes 17202 and 17204 may send the datastream (in the second compression format) to server 17206 in stages17314 b and 17316 b while the data stream is separated. In otheraspects, one of network access nodes 17202 or 17204 (e.g., networkaccess node 17202) may send the part of the data stream it received(e.g., the first part), the other network access node (e.g., networkaccess node 17204). This network access node (e.g., network access node17204) may then recombine the first and second parts to obtain the datastream in the second compression format, and may then send the datastream to server 17206. In such cases, server 17206 may then revert thesecond compression format in stage 17318 (e.g., may not performrecombination of the first and second parts).

This identification and addition of secondary spectrum may enableterminal device 17100 to reduce its power usage and/or reduce thelatency of the data stream while still being able to transfer the datastream (e.g., to meet the data rate demands of the data stream and/or tooptimize the overall stream time, which equals data transmission timeplus compression/decompression processing latency). In some aspects,terminal device 17100 may perform the procedure of message sequencechart 17300 in a continuous fashion. For example, controller 17102 maybe configured to periodically check the control variables to determinewhether the triggering condition is still satisfied (e.g., whether theremaining battery power level is still below the predefined remainingbattery power level threshold and/or the measured latency of the datastream is still above the predefined latency threshold). If controller17102 determines that the triggering condition is no longer satisfied(or, e.g., that another triggering condition is satisfied), controller17102 may switch back to the first compression format (or, e.g., switchto another compression format). Controller 17102 may release the secondspectrum and the second radio access connection, and then begin sendingthe data stream in the first compression format to network access node17202 on the primary spectrum.

As previously indicated, FIG. 174 shows message sequence chart 17400detailing the example of FIG. 172 in the downlink direction.Accordingly, instead of applying the compression format and sending thedata stream in the compression format to server 17206, terminal device17100 may be configured to receive the data stream in the compressionformat from server 17206 and revert the compression format to obtain thedata stream in its initial form. Accordingly, server 17206 may beconfigured to generate the data stream as a stream of user dataaddressed to stream application 17104. As shown in FIGS. 172 and 174 ,server 17206 may initially apply the first compression format to thedata stream in stage 17402 and send the data stream (in the firstcompression format) to network access node 17202 in stage 17404 b.Network access node 17202 may then wirelessly transmit the data streamover the first radio access channel (on the primary spectrum) toterminal device 17100 in stage 17404 a.

Terminal device 17100 may receive the wireless signals that include thedata stream at antenna 17114 and transceiver 17110, and may then revertthe first compression format in stage 17406. For example, afterprocessing the analog radio frequency signals provided by antenna 17114,transceiver 17110 may provide the data stream (in the first compressionformat) to router 17108. As terminal device 17108 is currently receivingthe data stream over the first radio access channel (e.g., and not thesecond radio access channel), controller 17102 may provide a routingselection signal to router 17108 that specifies that the data stream isunified (e.g., that recombination of a first and second parts isunnecessary). Router 17108 may therefore provide the data stream (in thefirst compression format) to digital compression processor 17106, whichmay revert the first compression format (e.g., as instructed by thecompression selection signal by controller 17102) to obtain the datastream in its initial format (e.g., as generated by server 17206).Digital compression processor 17106 may then provide the data stream tostream application 17104, thus completing transfer of the data streamover the software-level signaling connection.

Then, in stage 17408 terminal device 17100 may detect the triggeringcondition. For example, controller 17102 may detect the triggeringcondition in a same or similar manner as in stage 17308 of messagesequence chart 17300. For example, controller 17102 may receive controlvariables as input, such as a remaining battery power level of terminaldevice 17100, a measured latency of the data stream, and/or apower-saving mode indicator. Controller 17102 may then evaluate thecontrol variables to determine whether the triggering condition (or,e.g., which of a plurality of triggering conditions) is met. In somecases where the control variables include a measured latency of the datastream, stream application 17104 may be configured to measure thelatency of the data stream as it receives it over the software-levelconnection, and to provide this measured latency to controller 17102 asone of the control variables.

After detecting the triggering condition, terminal device 17100 mayidentify the second compression format and the secondary spectrum instage 17410. Similar to the case of FIG. 173 , terminal device 17100 mayuse a second radio access channel with network access node 17204 that ison the secondary spectrum. Accordingly, terminal device 17100 may detectand connect to network access node 17204 to set up the second radioaccess channel. In various aspects, controller 17102 may identify thesecond compression format and the secondary spectrum using anyfunctionality described for stage 17310 in message sequence chart 17300.

Terminal device 17100 may then send control signaling to server 17206(e.g., over the software-level signaling connection) in stage 17412 thatspecifies the second compression format and network access node 17204.For example, controller 17102 may send this control signaling to server17206. This may inform server 17206 of the second compression format(e.g., a compressed or uncompressed compression format) as well as thesecond network access node, e.g., network access node 17204, thatterminal device 17100 is using for the second spectrum.

Server 17206 may then apply the second compression format to the datastream and subsequently split the data stream into first and secondparts in stage 17414. Server 17206 may then send the first part tonetwork access node 17202 in stage 17416 b, and the second part tonetwork access node 17204 in stage 17418 b. Network access node 17202may then wirelessly transmit the first part of the data stream toterminal device 17100 over the first radio access channel on the primaryspectrum in stage 17416 a. Network access node 17204 may likewisewirelessly transmit the second part of the second stream to terminaldevice 17100 over the second radio access channel on the secondaryspectrum in stage 17418 a.

Terminal device 17100 may receive the wireless signals from networkaccess nodes 17202 and 17204 that include the first and second parts ofthe data stream (in the second impression format). Terminal device 17100may then recombine the first and second parts to obtain the data streamin the second compression format and subsequently revert the secondcompression format in stage 17420 to obtain the data stream in itsinitial format. For example, transceiver 17110 may receive the firstpart of the data stream on the first radio access channel via antenna17114, and may provide the first part of the data stream to router17108. Transceiver 17112 may likewise receive the second part of thedata stream on the second radio access channel via antenna 17116, andmay provide the second part of the data stream to router 17108. Router17108 may then recombine the first and second parts of the data streamto obtain the data stream in the second compression format (e.g., asinstructed by the routing selection signal from controller 17102).Router 17108 may provide the data stream to digital compressionprocessor 17106.

Digital compression processor 17106 may then revert the secondcompression format (e.g., as instructed by the compression selectionsignal from controller 17102). For example, if the second compressionformat is a compressed compression format, digital compression processor17106 may perform decompression processing on the data stream to revertthe second compression format. If the second compression format is anuncompressed compression format, digital compression processor 17106 mayrevert the second compression format by allowing the data stream to passthrough without decompression processing.

Digital compression processor 17106 may therefore obtain the data streamin its initial format (e.g., as generated by server 17206). Digitalcompression processor 17104 may then provide the data stream to streamapplication 17104, thus completing transfer of the data stream over thesoftware-level signaling connection.

Similar to that described above for message sequence chart 17300, insome aspects terminal device 17100 may perform the procedure of messagesequence chart 17400 continuously over time. For example, depending onwhether the control variables still meet the triggering condition,controller 17102 may switch back to the first compression format (and,for example, release the second spectrum and the second radio accessconnection) or may switch to another compression format (e.g., in thecase of a plurality of triggering conditions).

This use of dynamic compression format selection in the downlink mayyield similar advantages to the uplink case. For example, terminaldevice 17100 may be able to reduce its power usage by switching to asecond compression format with lower power usage (e.g., when terminaldevice 17100 has a remaining battery power level below a threshold or isin a power-saving mode) and/or to reduce the latency of the data stream(e.g., where stream application 17104 is a latency-sensitiveapplication) by switching to a second compression format with lowerlatency. As terminal device 17100 may introduce additional bandwidth viaintroduction of the second spectrum, terminal device 17100 may still beable to support transfer of the data stream even if the secondcompression format has lower compression efficiency (and thus a higherdata rate demand).

These examples described above for FIGS. 172-174 relate to a caseincluding where terminal device 17100 transfers the data stream on asecond radio access channel with a second network access node. FIGS.175-177 show an exemplary case according to some aspects where terminaldevice 17100 may transfer the data stream on secondary spectrum with thesame network access node as the primary spectrum. As shown in scenario17500 of FIG. 175 , terminal device 17100 may initially transfer thedata stream in a first compression format with network access node 17502on the primary spectrum, and may subsequently in scenario 17506 switchto transferring the data stream in a second compression format withnetwork access node 17502 on the primary and secondary spectrum.

FIG. 176 shows exemplary message sequence chart 17600 according to someaspects, which depicts the uplink case. Terminal device 17100, networkaccess node 17502, and server 17504 may perform stages 17602-17608 inthe same manner of stages 17302-17308 of message sequence chart 17300.Terminal device 17100 may therefore transmit the data stream in thefirst compression format to server 17504 via network access node 17502,and subsequently detect a triggering condition.

After detecting the triggering condition, terminal device 17100 mayidentify the second compression format and the secondary spectrum.However, instead of identifying secondary spectrum with another networkaccess node, terminal device 17100 may identify secondary spectrum thatterminal device 17100 can use to transmit the data stream to networkaccess node 17502. For example, terminal device 17100 may establish asecond radio access channel with network access node 17502 on thesecondary spectrum. Accordingly, in this example network access node17502 may support radio access channels on both the primary and thesecondary spectrum (e.g., using separate antennas and/or transceivers).Terminal device 17100 may use any technique described above for stage17310 in message sequence chart 17300 to identify the second compressionformat and the secondary spectrum.

Then, in stage 17612 terminal device 17100 may apply the secondarycompression format (e.g., with digital compression processor 17106) tothe data stream and split the data stream into first and second parts(e.g., with router 17108) in stage 17612.

Terminal device 17100 may then wirelessly transmit the first part of thedata stream on the primary spectrum over the first radio access channelwith network access node 17502 in stage 17614 a (e.g., with transceiver17110 and antenna 17114), and may wirelessly transmit the second part ofthe data stream on the secondary spectrum over the second radio accesschannel with network access node 17502 in stage 17616 a (e.g., withtransceiver 17112 and antenna 17116). In some aspects, stages 17614 aand 17616 a may occur at the same time, and in other aspects stages17614 a and 17616 a may occur at different times.

Network access node 17502 may then receive the first and second parts ofthe data stream on the first and second radio access channels, and maysend the first and second parts of the data stream to server 17504 instages 17614 b and 17616 b. Server 17504 may then receive the first andsecond parts of the data stream (in the second compression format),recombine the first and second parts, and revert the second compressionformat in stage 17618 to obtain the data stream in its initial format.In some aspects, network access node 17502 may recombine the first andsecond parts of the data stream before sending the data stream to server17504. In such cases, sever 17504 may not recombine the first and secondparts of the data stream before reverting the second compression format.In some aspects, terminal device 17100 may continuously repeat thisprocedure, such as to switch back to the first compression format or toswitch other compression formats.

Such cases where terminal device 17100 transmits the first and secondparts of the data stream can offer the same or similar advantages to thecase of FIGS. 172-174 . Accordingly, terminal device 17100 may be ableto reduce its power usage and/or reduce the latency of the data streamwhile still meeting the data rate demands of the data stream.

FIG. 177 shows exemplary message sequence chart 17700 illustrating thedownlink case according to some aspects. Accordingly, similar to as inmessage sequence chart 17400 of FIG. 174 , terminal device 17100 mayinitially receive the data stream in the first compression format fromserver 17504 via network access node 17502. Terminal device 17100,network access node 17502, and server 17504 may therefore perform stages17702-17708 in the same manner of stages 17402-17408 of message sequencechart 17400. After detecting the triggering condition in stage 17708,Terminal device 17100 may identify secondary spectrum and establish asecond radio access channel with network access node 17502. Terminaldevice 17100 may identify secondary spectrum and the second compressionformat in the same manner as any technique described above for stage17410.

Terminal device 17100 may then send control signaling to server 17504 instage 17712 that specifies that terminal device 17100 will receive thedata stream (in the second compression format) in first and second partsfrom network access node 17502. Server 17504 may therefore apply thesecond compression format to the data stream and split the data streaminto first and second parts in stage 17714. Server 17504 may then sendthe first and second parts to network access node 17502 in stages 17716b and 17718 b.

Network access node 17502 may then wirelessly transmit the first part ofthe data stream to terminal device 17100 on the first radio accesschannel on the primary spectrum in stage 17716 a. Network access node17502 may also wireless transmit the second part of the data stream toterminal device 17100 on the second radio access channel on thesecondary spectrum in stage 17718 a. Terminal device 17100 may thenreceive the first and second parts of the data stream (e.g., viaantennas 17114 and 17116 and transceivers 17110 and 17112), recombinethe first and second parts (e.g., with router 17108), and revert thesecond compression format to obtain the data stream in its initialformat in stage 17720. In some aspects, server 17504 may not split thedata stream into two parts in stage 17714, and may send the data stream(in the second compression format) to network access node 17502. Networkaccess node 17502 may then split the data stream into first and secondparts and wirelessly transmit the first and second parts to terminaldevice 17100 in stages 17716 a and 17718 a. In some aspects, terminaldevice 17100 may perform the procedure of message sequence chart 17700in a continuous manner, and may switch back to the first compressionformat or switch to another compression format depending on whether thetriggering conditions is still met (or, which of a plurality oftriggering conditions are met). Terminal device 17100 may therefore alsobe able to reduce its power usage and/or the latency of the data streamusing dynamic compression selection in a downlink case of FIG. 175 .

While described above with primary and secondary spectrum (e.g., firstand second spectrum), aspects of this disclosure can also use more thantwo radio access channels on different spectrum (e.g., with one, two, ormore than two network access nodes).

Additionally, in some aspects terminal device 17100 may be configured touse different compression formats for the first and second parts of thedata stream. FIG. 178 shows an exemplary internal configuration ofterminal device 17100 according to some aspects, which depicts oneexample of this use of different compression formats for the first andsecond parts of the data stream. As shown in FIG. 178 , router 17108 maybe positioned to separate the data stream into the first and secondparts (or, e.g., to recombine in the downlink direction), and providethem respectively to digital compression processor 17106 a and digitalcompression processor 17106 b. Digital compression processor 17106 a maythen apply a second compression format to the first part and provide thefirst part (in the second compression format) to transceiver 17110 forwireless transmission on the primary spectrum. Digital compressionprocessor 17106 a may then apply a third compression format (e.g.,different from the first and second compression formats) to the secondpart of the data stream and provide the second part (in the thirdcompression format) to transceiver 17112 for wireless transmission onthe secondary spectrum. In some aspects, controller 17102 may beconfigured to determine a target separation ratio that specifies therelative sizes of the first part and second part (e.g., the distributionof the data stream between the first radio access channel and the secondradio access channel). In some cases, controller 17102 can determine thetarget separation ratio based on, for example, the data rate and/orlatency of the first and second radio access channels, and can determinea target separation ratio that reduces (e.g., optimizes) the overallstreaming time (equal to the transmission time plus thecompression/decompression processing latency). Controller 17102 mayprovide this target separation ratio to router 17108, which may thensplit the data stream into the first and second parts according to thetarget separation ratio. In one example, the first radio access channelmay be a sub-6 GHz band, and digital compression processor 17106 a mayapply a compressed compression format due to the lower data ratessupported by the sub 6-GHz band, while the second radio access channelmay be a high frequency band (e.g., above 23 GHz) and digitalcompression processor 17106 a may use an uncompressed compressionformat.

The second and third compression formats may have different power usage,latency, and/or compression efficiency characteristics, but may havelower power usage and/or latency than the first compression format.Accordingly, terminal device 17100 may be able to use differentcompression formats for the primary and secondary spectrum and stillreduce latency and/or power consumption compared to the firstcompression format.

The functionality of controller 17102 is described above as beingimplemented in a terminal device. This functionality, includingevaluation of control variables, selection of secondary spectrum, andselection of a second compression format, can additionally oralternatively be complemented in another location. For example, in someaspects a network access node may be configured in the manner of networkaccess node 110 shown in FIG. 3 , and may include controller 17102 inits protocol controller 310. Controller 17102 may therefore evaluate thecontrol variables, select the secondary spectrum, and select secondcompression formats, and may send control signaling to terminal devicesand/or servers that specify the secondary spectrum and secondcompression formats. In other aspects, controller 17102 may beimplemented in an edge network server, a core network server, or at anexternal Internet server (e.g., as part of server 17206 or 17504 or as aseparate external Internet server). Controller 17102 may likewiseevaluate the control variables, select the secondary spectrum, andselect second compression formats, and may send control signaling toterminal devices and/or servers that specify the secondary spectrum andsecond compression formats.

FIG. 179 shows exemplary method 17900 of transferring a data stream at acommunication device according to some aspects. As shown in FIG. 179 ,method 17900 includes transmitting or receiving a data stream in a firstcompression format with first spectrum (17902), detecting a triggeringcondition based on a power status of the communication device or alatency parameter of the data stream, and selecting a second compressionformat and second spectrum (17904), and transmitting or receiving thedata stream in the second compression format with the first and secondspectrum (17906).

FIG. 180 shows exemplary method 18000 of transferring a data stream at acommunication device. As shown in FIG. 180 , method 18000 includestransmitting or receiving a data stream in a first compression formatwith first spectrum (18002), detecting a triggering condition based on apower status of the communication device or a latency parameter of thedata stream, and selecting an uncompressed compression format and secondspectrum (18004), and transmitting or receiving the data stream in theuncompressed compression format with the first and second spectrum(18006).

FIG. 181 shows exemplary method 18100 of transferring a data stream at acommunication device according to some aspects. As shown in FIG. 181 ,method 18100 includes transmitting or receiving a data stream in a firstcompression format with first spectrum (18102), detecting a triggeringcondition based on a power status of the communication device or alatency parameter of the data stream (18104), and transmitting orreceiving a first part of the data stream with a second compressionformat on the first spectrum and transmitting or receiving a second partof the data stream with a third compression format on second spectrum(18106).

Dynamic Modulation Scheme Selection with Battery Power Status

Some radio access technologies may employ adaptive modulation schemeselection. In one example, LTE networks utilize variable modulationschemes to adapt the modulation scheme for uplink and downlinkcommunications. Accordingly, a network access node may be able toadaptively assign a modulation scheme to a served terminal device, suchas by selecting an appropriate modulation scheme based on the currentradio access channel between the network access node and the servedterminal device.

The use of different modulation schemes by a terminal device may impactperformance. In particular, terminal devices may be able to achievehigher data rates with higher-order modulation schemes. For example, aterminal device using a Quadrature Amplitude Modulation (QAM) scheme,such as 16-QAM, may be able to encode more data into each modulationsymbol (e.g., 4 bits per modulation symbol) than a terminal device usinga Phase Shift Keying (PSK) modulation scheme, such as Binary PSK (BPSKe.g., 1 bit per modulation symbol). Terminal devices may therefore beable to achieve progressively higher data rates based on whether theyuse BPSK, Quadrature PSK (QPSK), 8-PSK, 32-QAM, 64-QAM, 128-QAM,256-QAM, and any other higher-order scheme (listed here in increasingorder of bits per symbol/data rate).

However, as recognized by this disclosure, some modulation schemes maybe less power efficient than other modulation schemes. For example,hybrid amplitude-phase modulation schemes such as QAM schemes may beless power efficient than modulation schemes based purely on phasemodulation (e.g., BPSK). By extension, higher-order modulation schemes(e.g., 64-QAM) may be less power efficient than lower-order modulationschemes (e.g., QPSK). Such differences in power efficiency can arisefrom the extra power that is expended by the power amplifier (PA) whentransmitting modulation symbols from more complex symbol constellations.For instance, the amplitude differences in the various symbols of a QAMconstellation can result in power efficiency of only about 15% at thepower amplifier, while the same power amplifier may be able to operateat around 50% when using a purely phase-based modulation such as BPSK.Higher-order QAM schemes may use a higher power backoff from the pointof maximum power added efficiency (PAE) of the power amplifier. Poweramplifier can be very linear at low efficiency power amplifier is verylinear, which can therefore allow for higher-order modulation schemes.By contrast, at high efficiency the power amplifiers can be verynonlinear in terms of amplitude to phase distortion (AM-PM) and gainexpansion. This power amplifier nonlinearity can be measured andcharacteristic by the error vector magnitude (EVM) of the modulationconstellation diagram, which characterizes the error between the idealmodulation symbol (on the modulation constellation diagram) and theactual transmitted symbol.

In some cases, low power efficiency can become particularly problematicfor terminal devices, many of which operate on battery power thatgradually depletes over time. A terminal device using a QAM scheme mayexpend battery power at a faster rate than when using a PSK scheme. Thispower expenditure can be aggravated at mmWave frequencies, where the PAEis particularly low due to the decreased gain of transistors andincreased loss in passive devices (e.g., coils, transformers,transmission lines, capacitors) with increasing frequency.

Accordingly, various aspects of this disclosure introduce the batterypower status of a terminal device as a control variable for themodulation scheme selection function. As further described herein, anetwork access node can therefore be configured to evaluate the batterypower status of a terminal device and subsequently render modulationscheme decisions based on the battery power status. In some aspects,this modulation scheme selection function can be expanded to considerother control variables (e.g., in addition to battery power status) whenselecting modulation schemes for terminal devices. For example, in someaspects a network access node may also select a modulation scheme for aterminal device based on a distance between the network access node andthe terminal device. In particular, terminal devices that are locatedfurther from a network access node may use a higher transmit power thanterminal devices that are proximate to the network access node. However,use of this higher transmit power may also lead to faster batterydepletion at the terminal device. Accordingly, as described below forsome aspects, the network access node may therefore be configured toselect a modulation scheme for the terminal device based on its distanceto the network access node, such as by selecting a more power efficientmodulation scheme for a terminal device that has low remaining batterypower and is far from the network access node.

Various aspects may introduce further control variables into themodulation scheme selection function, such as network access node powerusage and terminal device temperature. In some aspects, the networkaccess node may also consider the data rate demands of a data streamthat the terminal device is transmitting, as the use of more powerefficient modulations schemes may also reduce the maximum data rate. Insome of these aspects, the network access node may also consider theavailability of spectrum offload, such as whether the terminal device isable to initiate a second radio access channel on secondary spectrumthat could also be used to transfer the data stream, where the secondaryspectrum offering a larger bandwidth that allows for high data rate witha lower order modulation scheme. Such aspects are further describedherein.

FIG. 182 shows an example of a network communication scenario accordingto some aspects. As shown in FIG. 182 , terminal device 18202 may betransmitting data to network access node 18204 using a first radioaccess channel and a first modulation scheme. In some aspects, terminaldevice 18202 may be configured in the manner of terminal device 102 asshown in FIG. 2 , and accordingly may include antenna system 202, RFtransceiver 204, and baseband modem 206. When transmitting to networkaccess node 18204, baseband modem 206 may generate modulation symbols(e.g., representing user or control data from higher layers) accordingto a modulation scheme, e.g., a first modulation scheme. Baseband modem206 may provide these modulation symbols to RF transceiver 204, whichmay apply digital-to-analog conversion (DAC), RF mixing, andamplification to transmit the modulation symbols in the form of wirelesssignals via antenna system 202.

As previously indicated, the type of modulation scheme may impact thepower usage of RF transceiver 204. For example, the power amplifier ofRF transceiver 204 may expend more power (e.g., be less power efficient)when the modulation scheme is a hybrid amplitude-phase modulation scheme(e.g., any QAM scheme) than when the modulation scheme is aphase-shifting modulation scheme (e.g., any PSK scheme) or a frequencymodulation (FM) scheme. Likewise, the power amplifier of RF transceiver204 may be less power efficient when the modulation scheme is ahigher-order modulation scheme. This can be problematic when terminaldevice 18202 is powered by a battery power supply, as the remainingbattery power level may gradually deplete as terminal device 18202operates. Battery drain may therefore be higher in scenarios when thepower amplifier is operating in a low power efficiency state, such aswhen terminal device 18202 is using a QAM or higher-order modulation(e.g. 16-QAM, 64-QAM, 256-QAM) scheme, which can require a higher powerbackoff from the point of maximum PAE of the power amplifier in thetransmitter.

Accordingly, in some aspects network access node 18204 may be configuredto consider the battery power status of terminal device 18202 as acontrol variable in its modulation scheme selection function (e.g., whenselecting a modulation scheme for terminal device 18202 to use in theuplink direction). FIG. 183 shows an exemplary internal configuration ofnetwork access node 18204, which will be used to describe the modulationscheme selection function according to some aspects. As shown in FIG.183 , network access node 18204 may include antenna system 18302,communication subsystem 18308 (including transmitter 18304 and receiver18306), and scheduler 18310. In some aspects, antenna system 18302 maybe configured in the manner of antenna system 302 previously describedfor network access node 110 of FIG. 3 . Transmitter 18304 and receiver18306 of communication subsystem 18308 may therefore be configured totransmit and receive wireless signals via antenna system 302.Transmitter 18304 may be a transmitter including various transmissioncomponents of network access node 18204. This can include, for example,an RF transceiver with a power amplifier, physical layer transmissioncircuitry and controllers, and/or baseband subsystem transmissioncomponents. Receiver 18306 may be a receiver including various receptioncomponents of network access node 18204. This can include, for example,an RF transceiver with a low-noise amplifier, physical layer receptioncircuitry and controllers, and/or baseband subsystem receptioncomponents. Communication subsystem 18308 can therefore include any oneor more of RF components, physical layer components, or basebandsubsystem components, and is not specifically limited to exclusivelyincluding any one of these types of components.

Scheduler 18310 may be a special-purpose processor configured toevaluate one or more control variables that network access node 18204uses for the modulation scheme selection function. As described belowfor various aspects, these control variables can include a battery powerstatus of a terminal device, a distance of the terminal device fromnetwork access node 18204, a temperature of the terminal device, acharging status of the terminal device, power amplifier characteristicsof the terminal device, data rate demands of a data stream of theterminal device, spectrum offload information for the terminal device,and/or power usage of network access node 18204. Schedule 18310 maytherefore be configured to evaluate one or more of these controlvariables and to select a modulation scheme for the terminal devicebased on the control variables.

FIG. 184 shows exemplary message sequence chart 18400 according to someaspects, which illustrates an exemplary procedure of the modulationscheme selection function. As shown in FIG. 184 , terminal device 18202may first determine its battery power status in stage 18402. In someaspects, the battery power status can be a remaining battery powerlevel. For example, in some aspects where terminal device 18202 isconfigured in the manner of terminal device 102 described above for FIG.2 , application processor 212 may determine a remaining battery powerlevel of the battery power supply of terminal device 18202. Applicationprocessor 212 may then specify the remaining battery power level toprotocol controller 210 of terminal device 18202. Protocol controller210 may then generate a battery power status report that includes theremaining battery power level.

In other aspects, the battery power status can be a power-saving modeindicator. For example, in some aspects a user may have the option toselectively enable a power-saving mode for terminal device 18202. Thismay be an application-layer function, and application processor 212 ofterminal device 18202 may therefore detect when the user enables ordisables the power-saving mode. When the user enables the power-savingmode, application processor 212 may provide a power-saving modeindicator to protocol controller 210 that specifies that thepower-saving mode is enabled. Protocol controller 210 of terminal device18202 may then generate a battery power status report that includes thepower-saving mode indicator. In some aspects, there may be multiplepower-saving modes (e.g., in addition to a standard power mode), whereeach of the power-saving modes targets a different level ofpower-savings. In such cases, the power-saving mode indicator mayindicate which of the power-saving modes is enable (out of the multiplepower-saving modes).

In some aspects, the battery power status can be an estimated batterypower usage. For example, terminal device 18202 may be transmitting aparticular data stream with a finite size or duration. Accordingly,protocol controller 210 of terminal device 18202 may estimate thebattery power that will be expended in transmitting the data stream. Insome cases, protocol controller 210 may be configured to estimatemultiple battery power usages, such as by estimating a different batterypower usage for transmitting the data stream with different modulationschemes. Protocol controller 210 may be configured to perform thisestimation, for example, based on power amplifier characteristics of thepower amplifier in RF transceiver 204. For example, the power amplifiercharacteristics may be a priori information that characterizes theefficiency of the power amplifier (e.g., PAE). The power amplifiercharacteristics may, in some aspects, specify different powerefficiencies at different frequencies and/or at different modulationschemes, which protocol controller 210 may use to estimate the batterypower usage. Protocol controller 210 may generate a battery power statusreport that includes this estimated battery power usage.

In some aspects, the battery power status can include multiple of aremaining battery power level, a power-saving mode indicator, or anestimated battery power usage. Accordingly, protocol controller 210 ofterminal device 18202 may generate a battery power status report thatincludes multiple or all of the remaining battery power level, thepower-saving mode indicator, and the estimated battery power usage.

After generating the battery power status report, terminal device 18202may send the battery power status report to network access node 18204 instage 18404. For example, protocol controller 210 may wirelesslytransmit the battery power status report via digital signal processor208, RF transceiver 204, and antenna system 202. Network access node18204 may then receive the battery power status report via antennasystem 18302 and receiver 18306. Receiver 18306 may then provide thebattery power status report to scheduler 18310, which may read thebattery power status report to determine the battery power status (e.g.,a remaining battery power level and/or a power-saving mode indicator).

Network access node 18204 may then execute the modulation schemeselection function to select a modulation scheme for terminal device18202 based on the battery power status in stage 18406. In one example,terminal device 18202 may initially be assigned a first modulationscheme. Scheduler 18310 may therefore select a second modulation schemefor terminal device 18202 based on the battery power status. Forexample, in some aspects where the battery power status is a remainingbattery power level, scheduler 18310 may compare the remaining batterypower level to a threshold (e.g., that is selected to indicate lowremaining battery power at terminal device 18202, such as 10%, 20%, oranother selected level). In some aspects, the threshold can bepredefined, while in other aspects the threshold can be dynamicallyadjusted or selected (e.g., based on user settings, scheduled deviceoperations, or another criteria related to remaining battery powerlevel). If scheduler 18310 determines that the remaining battery powerlevel is less than the threshold, scheduler 18310 may be configured toselect a second modulation scheme for terminal device 18202 that is morepower efficient than the first modulation scheme (e.g., that has lowermodulation order than the first modulation scheme, or is a PSKmodulation scheme compared to a first modulation scheme that is a QAMscheme). Accordingly, when the remaining battery power level of terminaldevice 18202 is low (e.g., less than the threshold), scheduler 18310 maybe configured to select a power-efficient modulation scheme. In someaspects, scheduler 18310 may be configured to maintain the firstmodulation scheme for terminal device 18202 (e.g., not to select asecond modulation scheme) if the remaining battery power level isgreater than the threshold.

In some aspects, scheduler 18310 may be configured to use a predefinedmapping to select the modulation scheme in stage 18406. For example, thepredefined mapping may map different battery power statuses torespective modulation schemes. Accordingly, scheduler 18310 may applythe predefined mapping to identify a modulation scheme to which thebattery power status of terminal device 18202 maps, and may then selectthis modulation scheme as the modulation scheme in stage 18406. In oneexample where the battery power status is a remaining battery powerlevel, the predefined mapping may map different ranges of remainingbattery power levels to respective modulation schemes. The predefinedmapping may progressively map lower ranges of remaining battery powerlevel to more power-efficient modulation schemes (e.g., to modulationschemes with lower modulation order). For example, the predefinedmapping may map a lowest range of remaining battery power levels (e.g.,10% or less) to a BPSK scheme, a second-lowest range of remainingbattery power levels to a QPSK scheme, a third-lowest range of remainingbattery power levels to an 8-PSK scheme, a fourth-lowest range ofremaining battery power levels to a 16-QAM scheme, a fifth-lowest rangeof remaining battery power levels to a 32-QAM scheme, and a sixth-lowestrange of remaining battery power levels to a 64-QAM scheme. Scheduler18310 may therefore identify the range of the predefined mapping inwhich the remaining battery level falls and identify the respectivemodulation scheme to which it is mapped. Scheduler 18310 may then selectthis modulation scheme as the modulation scheme for terminal device18202. Accordingly, scheduler 18310 may select the modulation schemebased on whether the remaining battery power level satisfies apredefined condition, such as which modulation scheme the remainingbattery power level maps to according to the predefined mapping (e.g.,which range of the predefined mapping the remaining battery power levelmaps to). In some aspects, this predefined mapping can be implemented asa lookup table.

As the predefined mapping maps lower remaining battery power levels tomore power efficient modulation schemes, scheduler 18310 may beconfigured to select a more power efficient modulation scheme whenterminal device 18202 has low remaining battery power. Accordingly, thisintroduction of remaining battery power level of terminal device 18202as a control variable to the modulation scheme selection function mayhelp prolong the battery life of terminal device 18202.

As previously indicated, in some cases the battery power status (e.g.,included in the battery power status report) may be a power-saving modeindicator. This power-saving mode indicator may indicate whether apower-saving mode is enabled at terminal device 18202 (or, in the caseof multiple power-saving modes, which power-saving mode is enabled). Insome aspects, scheduler 18310 may be configured to select a firstmodulation scheme when the power-saving mode indicator specifies thatthe power-saving mode is enabled and to select a second modulationscheme when the power-saving mode indicator specifies that thepower-saving mode is not enabled (e.g., equivalent logic to a lookuptable with two entries). The first modulation scheme may have a higherpower efficiency than the second modulation scheme, which may thereforeresult in terminal device 18202 being assigned a more power efficientmodulation scheme when the power-saving mode is enabled.

In one example, terminal device 18202 may initially be assigned a firstmodulation scheme. Scheduler 18310 may then be configured to select asecond modulation scheme for terminal device 18202 based on thepower-saving mode indicator in stage 18406. For example, scheduler 18310may be configured to determine whether the power-saving mode indicatorindicates that the power-saving mode at terminal device 18202 isenabled. If scheduler 18310 determines that the power-saving mode isenabled, scheduler 18310 may be configured to select a second modulationscheme for terminal device 18202 that is more power efficient than thefirst modulation scheme (e.g., that has lower modulation order than thefirst modulation scheme, or is a PSK modulation scheme compared to afirst modulation scheme that is an QAM scheme). Accordingly, when thepower-saving mode is enabled, scheduler 18310 may be configured toselect a power-efficient modulation scheme. In some aspects, ifscheduler 18310 determines that the power-saving mode indicatorindicates that the power-saving mode is not enabled, scheduler 18310 maybe configured to maintain the first modulation scheme for terminaldevice 18202 (e.g., not to select a second modulation scheme).

In some aspects, such as where the power-saving mode indicator indicateswhich of multiple power-saving modes is enabled at terminal device18202, scheduler 18310 may be configured to use a predefined mappingthat maps each power-saving mode to a prescribed modulation scheme. Thepredefined mapping may map power-saving modes that have higher targetedpower-savings (e.g., to prolong battery live the longest/to slow batterydepletion the most) to modulation schemes that have the highestpower-efficiency. Scheduler 18310 may therefore select more powerefficient modulation schemes when a user of terminal device 18202 hasselected a power-saving mode with higher targeted power saving. In someaspects, this predefined mapping can be implemented as a lookup table.

In some aspects where the battery power status report includes anestimated battery power usage, scheduler 18310 may select a secondmodulation scheme for terminal device 18202 based on the estimatedbattery power usage. In one example, the battery power status report mayinclude both a remaining battery power level and an estimated batterypower usage (estimated by protocol controller 210 of terminal device18202). The estimated battery power usage may indicate the estimatedamount of battery power that terminal device 18202 will expend whiletransmitting the data stream with a first modulation scheme. Scheduler18310 may then evaluate the remaining battery power level and theestimated battery power usage, and select a second modulation scheme forterminal device 18202 based on the remaining battery power level and theestimated battery power usage. In one example, scheduler 18310 maydetermine an estimated remaining battery power level as the differencebetween the remaining battery power level and the estimated batterypower usage. If this estimated remaining battery power level is lessthan a threshold (e.g., 0%, meaning terminal device 18202 is estimatedto use all of its battery power to transmit the data stream with thefirst modulation scheme, or another threshold, such as 10%, 20%, etc.),scheduler 18310 may select a second modulation scheme that is morepower-efficient than the first modulation scheme (e.g., a lower-ordermodulation scheme than the second modulation scheme). In anotherexample, scheduler 18310 may compare the estimated battery power usageto a threshold, and may select a second modulation scheme that is morepower-efficient than the first modulation scheme if the estimatedbattery power usage is greater than a threshold. In another example,scheduler 18310 may use a predefined mapping that maps differentestimated battery power usages to different modulation schemes to selectthe second modulation scheme, where the predefined mapping may maphigher estimated battery power usages to lower-order modulation schemes.In another example where the battery power status report includesmultiple estimated battery power usages that are each estimated for adifferent modulation scheme (as estimated by protocol controller 210 ofterminal device 18202), scheduler 18310 may select the second modulationscheme based on the multiple estimated battery power usages. Forinstance, scheduler 18310 may identify the highest estimated batterypower usage that is less than a predefined threshold, and select thecorresponding modulation scheme (used by protocol controller 210 todetermine the estimated battery power usage) as the second modulationscheme. In some aspects, scheduler 18310 may determine the estimatedbattery power usage locally (e.g., based on power amplifiercharacteristics provided by protocol controller 210 of terminal device18202 in the battery power status report), and may then apply any ofthese techniques locally with the estimated battery power usage toselect the second modulation scheme.

In some aspects, scheduler 18310 may select a modulation scheme forterminal device 18202 based on a user profile of terminal device 18202.For example, scheduler 18310 may have a user profile for terminal device18202 that is individually specific to terminal device 18202, such asbased on past user behavior of terminal device 18202. In one example,these user profiles can be based on cognitive neural networks, whichscheduler 18310 or another network component (e.g., in the cloud or partof the core network) may use to develop the user profiles for multipleterminal devices based on observed behavior for each terminal device.The user profiles may be based on power usage, and may thereforeindicate future power usage of terminal device 18202 based on its pastbehavior. In some aspects, scheduler 18310 may use the user profile toselect a second modulation scheme for terminal device 18202, such as byidentifying terminal device 18202 (e.g., based on device identity) andretrieving the user profile for terminal device 18202. In one example,the user profile may indicate that terminal device 18202 has a highestimated battery power usage (e.g., in an upcoming period of time, suchas over the next hour, several hours, or day). Scheduler 18310 may thenselect a second modulation scheme that is more power efficient than thefirst modulation scheme.

In some aspects, scheduler 18310 may also consider a link quality of theradio access channel between terminal device 18202 and network accessnode 18204. For example, protocol controller 210 of terminal device18202 may generate and transmit a measurement report to network accessnode 18204. Scheduler 18310 may then select the modulation scheme basedon the battery power status and the link quality in stage 18406. Thiscan help to avoid scenarios where terminal device 18202 uses amodulation scheme that has high order in low link quality scenarios(e.g., as higher-order modulation schemes may perform sub-optimally whenthere is low SNR). In some aspects, scheduler 18310 may be configured touse a predefined mapping, such as a two-dimensional lookup table, thatmaps remaining battery power level and link quality to prescribedmodulation schemes (e.g., that maps pairs of remaining battery powerlevels and link qualities to prescribed modulation schemes).Accordingly, given the remaining battery power level and the linkquality, scheduler 18310 may use the predefined mapping to identify theprescribed modulation scheme that is mapped to the remaining batterypower level and the link quality. This predefined mapping may mapprogressively higher link qualities to higher-order modulation schemes(e.g., less power-efficient modulation schemes) and progressively lowerremaining battery power levels to more power efficient modulationschemes (e.g., higher-order modulation schemes).

In some aspects, scheduler 18310 may be configured to likewise use apredefined mapping, such as a two-dimensional lookup table, that maps apower-saving mode and a link quality to a prescribed modulation scheme.For example, the predefined mapping may map power-saving modes withprogressively higher targeted power saving to progressively morepower-efficient modulation schemes, and map progressively higher linkqualities to progressively less power-efficient modulation schemes.

Various examples above describe implementation of the selection logic ofthe modulation scheme selection function with predefined mappings suchas lookup tables. This is only one example of selection logic that canbe used by scheduler 18310 to select the modulation scheme in stage18406 based on the battery power status. For example, in some aspectsscheduler 18310 may use a modulation scheme selection equation (e.g., apredefined equation) that has input variables for battery power status(e.g., a variable in the modulation scheme selection equation forremaining battery power level and/or a variable in the modulation schemeselection equation for a power-saving mode indicator) and/or for linkquality (e.g., a variable in the modulation scheme equation for a linkquality metric, such as SNR). The output variable of the modulationscheme selection equation may be a modulation scheme. In some aspects,the modulation scheme selection equation may include predefined weightsassigned to the input variables, where an input variable with a largerweight may cause the value of the input variable to have a greaterimpact on the output variable (e.g., have greater impact in selecting aparticular modulation scheme). For example, in some cases remainingbattery power level may be a key control variable, and the modulationscheme selection equation may therefore define a higher weight for theremaining battery power level (and/or for any other key controlvariable). Scheduler 18310 may therefore in stage 18406 evaluate themodulation scheme selection equation by using the actual values forthese input variables and obtaining a modulation scheme as the outputvariable. Scheduler 18310 may then select this modulation scheme instage 18406.

Scheduler 18310 may be configured to select the modulation scheme basedon the battery power status in stage 18406 according to any of thesevariations. In some aspects, terminal device 18202 may have initiallybeen assigned a first modulation scheme, and scheduler 18310 may selecta second modulation scheme in stage 18406 (e.g., that is morepower-efficient than the first modulation scheme). After selecting themodulation scheme for terminal device 18202, scheduler 18310 maygenerate a modulation scheme assignment message that specifies themodulation scheme in stage 18408. Scheduler 18310 may then transmit themodulation scheme assignment message to terminal device 18202 in stage18410 (e.g., via transmitter 18306 and antenna system 18302).

Terminal device 18202 may then receive the modulation scheme assignmentmessage and begin transmitting according to the modulation schemespecified in the modulation scheme assignment message in stage 18412.For example, protocol controller 210 of terminal device 18202 may readthe modulation scheme assignment message and identify the modulationscheme. Protocol controller 210 may then instruct digital signalprocessor 208 of terminal device 18202 to use the modulation scheme fortransmission. Digital signal processor 208 may then apply the modulationscheme when mapping data blocks to modulation symbols for uplinktransmission to network access node 18204. Network access node 18204 maythen receive data with receiver 18306 that is modulated according to themodulation scheme.

Accordingly, in scenarios where terminal device 18202 has low remainingbattery power level or is in a power-saving mode, scheduler 18310 may beconfigured to assign a more power efficient modulation scheme toterminal device 18202 (e.g., according to the mappings in the lookuptable). The power amplifier of RF transceiver 204 in terminal device18202 may therefore amplify signals generated with a more powerefficient modulation scheme, which will in turn improve the powerefficiency of the power amplifier. This can therefore help to reducepower consumption at terminal device 18202 and to likewise improve itsbattery life.

In some aspects, the modulation scheme selection function may introducefurther control variables (e.g., in addition to battery power statusand/or link quality). FIG. 185 shows exemplary message sequence chart18500 according to some aspects, which describes an exemplary usage ofother control variables in the modulation scheme selection function. Asshown in FIG. 185 , terminal device 18202 may determine its batterypower status and send a battery power status report in stages 18502 and18504 (e.g., in the same manner described above for stages 18402 and18404 in FIG. 184 ).

Terminal device 18202 may also send an additional control variablereport (or multiple additional control variables reports) to networkaccess node in stage 18506, which may include other control variables.In one example, the additional control variable report can include acurrent position of terminal device 18202. For example, protocolcontroller 210 of terminal device 102 may obtain a current position ofterminal device 18202 (e.g., via a satellite-based positioning function,as a positioning function based on GNSS) and may include the currentposition in the additional control variable report when sending it tonetwork access node 18204. In another example, the additional controlvariable report can include a signal strength measurement by terminaldevice 18202. For example, digital signal processor 208 of terminaldevice 18202 may perform a signal strength measurement on a signalreceived from network access node 18204, and may provide the signalstrength measurement to protocol controller 210. Protocol controller 210may then include the signal strength measurement as a control variablein the additional control variable report in stage 18506.

In another example, the additional control variable report canadditionally or alternatively include a temperature measurement ofterminal device 18202. For example, protocol controller 210 of terminaldevice 102 may obtain a temperature measurement of terminal device 18202(e.g., with a thermometer or other temperature sensor of terminal device18202), and may include the temperature measurement in the additionalcontrol variable report when sending it to network access node 18204. Invarious aspects, the temperature measurement can, for example, be acurrent temperature, a current temperature of a specific component ofterminal device 18202 (e.g., its power amplifier), or aslope/rate-of-change over recent temperature measurements. In someaspects, protocol controller 210 may also include a temperaturethreshold as one of the control variables, such as a temperaturethreshold that indicates a maximum permissible temperature level forterminal device 18202.

The charging status can indicate whether terminal device 18202 iscurrently charging its battery power supply. In one example, applicationprocessor 212 may have application-layer information that indicateswhether the battery power supply is charging or not, and may report thecorresponding charging status to protocol controller 210. Protocolcontroller 210 may then include the charging status in the additionalcontrol variable report.

In another example, the additional control variable report can includepower amplifier characteristics of terminal device 18202. These poweramplifier characteristics may indicate PAE metrics of the poweramplifier of terminal device 18202, such as different PAE metrics fordifferent modulation schemes and/or different frequency bands. Thisinformation may be known a priori at protocol controller 210, andprotocol controller 210 may therefore include these power amplifiercharacteristics in the additional control variable report.

In another example, the additional control variable report can includedata stream parameters that describe a data stream that terminal device18202 is transmitting. For example, application processor 212 ofterminal device 18202 may be transmitting a data stream of user data(e.g., to an external internet server that acts as an applicationendpoint for the data stream), where the data stream may have certainQuality of Service (QoS) parameters. In one example, the data stream mayhave a data rate demand (e.g., a minimum data rate), which applicationprocessor 212 may specify to protocol controller 210. Protocolcontroller 210 may then include the data rate demand in the additionalcontrol variable report.

In another example, the additional control variable report can includespectrum offload information that indicates whether terminal device18202 supports spectrum offload. For example, in some aspects terminaldevice 18202 may be configured to support multiple radio access channelson multiple bands. This can include where RF transceiver 204 of terminaldevice 18202 includes a first transceiver configured for operation onfirst spectrum (e.g., primary spectrum) and a second transceiverconfigured for operation on second spectrum (e.g., secondary spectrum).As terminal device 18202 is therefore able to support multiple radioaccess channels on multiple bands (e.g., at least the first and secondspectrum), protocol controller 210 may include spectrum offloadinformation in the additional control variable report that indicatesthat terminal device 18202 to supports spectrum offload.

In some aspects, terminal device 18202 may send the battery power statusreport and the additional control variable report to network access node18204 in the same message. In other aspects, terminal device 18202 maysend the battery power status report and the additional control variablereport to network access node 18204 in different messages. In someaspects where terminal device 18204 sends multiple types of additionalcontrol variables (e.g., multiple of a current position, temperature,power amplifier characteristics, charging status, data streamparameters, and/or spectrum offload information), terminal device 18204may be configured to send multiple additional control variable reportsin stage 18506.

Network access node 18204 may then collect control variables in stage18508. For example, scheduler 18310 may receive the battery power statusreport and additional control variable report from terminal device18202, and may read the battery power status report and additionalcontrol variable report to identify the control variables (e.g., any ofremaining battery power level, power-saving mode indicator, poweramplifier characteristics, temperature, charging status, currentposition, and/or signal strength).

In some aspects, scheduler 18310 may read the current position ofterminal device 18202 from the additional control variable report, andmay then determine the distance between terminal device 18202 andnetwork access node 18204 based on the current position (e.g., bydetermining the difference between the current position of terminaldevice 18202 and the position of network access node 18204). Scheduler18310 may then use this distance as a control variable. In some aspects,scheduler 18310 may read the signal strength measurement of terminaldevice 18202, and may estimate the distance between terminal device18202 and network access node 18204 based on the signal strengthmeasurement. Scheduler 18310 may also use this distance as a controlvariable. In other cases, scheduler 18310 may be configured to estimatethe position of terminal device 18202 locally, such as by usingtriangulation in coordination with other network access nodes (e.g., insmall cell using mm-Wave and beamforming), and may use this position forterminal device 18202.

In some cases, network access node 18204 may collect other controlvariables. In one example, the control variables can also include apower usage level of network access node 18204. For example, scheduler18310 may be configured to determine a power usage level of networkaccess node 18204 (e.g., a metric that quantities the power usage ofnetwork access node 18204 over an interval of time), and to use thispower usage level as a control variable in stage 18508.

Scheduler 18310 may then select a modulation scheme for terminal device18202 based on the control variables in stage 18510. As indicated above,the control variables can include any of a battery power status (e.g.,remaining battery power level and/or power-saving mode indicator), alink quality metric, a current position, a signal strength measurement,a distance, a temperature measurement, power amplifier characteristics,charging status, data stream parameters, and/or spectrum offloadinformation. Scheduler 18310 may therefore apply selection logic for themodulation scheme selection function to select a modulation scheme basedon the control variables.

In various aspects, scheduler 18310 may be configured to select themodulation scheme from a predefined set of modulation schemes. Aspreviously described, the modulation schemes may vary in terms of powerefficiency, where higher-order and QAM schemes may be less powerefficient (but have support data rates) than lower-order and PSKschemes. As the control variables may relate to various power-efficiencyconcerns of terminal device 18202, scheduler 18310 may be configured toselect the modulation scheme based on the power-efficiencycharacteristics indicated by the control variables.

In some aspects, scheduler 18310 may be configured to use a predefinedmapping between the control variables and a set of modulation schemes toselect the modulation scheme in stage 18510. For example, the set ofmodulation schemes may include the modulation schemes available for use,such as a set including BPSK, QPSK, 8-PSK, 16-QAM, 32-QAM, and 64-QAM(and, optionally, higher orders of QAM). Accordingly, scheduler 18310may use a predefined mapping that maps different values of the controlvariables to specified modulation schemes. In some aspects, thispredefined mapping can be embodied as a multi-dimensional lookup table,such as where each dimension corresponds to a different control variableand input of the control variables for each dimension maps to aparticular modulation scheme (e.g., an entry of the lookup table that ismapped to the particular values of the control variables, where theparticular values represent a predefined condition). Accordingly,scheduler 18310 may start with the control variables (e.g., any ofremaining battery power level, power-saving mode indicator, estimatedbattery power usage, a link quality metric, a current position, a signalstrength measurement, a distance, power amplifier characteristics, atemperature measurement, charging status, data stream parameters, and/orspectrum offload information), and may use the values of the controlvariables to identify a corresponding entry of the lookup table that ismapped to the values of the control variables and contains one of theset of modulation schemes. Scheduler 18310 may then select thismodulation scheme in stage 18510.

In some aspects, the predefined mapping may be configured to select morepower-efficient modulation schemes when the control variables havecertain values (e.g., meet a predefined condition). For example,scheduler 18310 may be configured to select a more power-efficientmodulation scheme when a remaining battery power level is a first valuethan when the remaining battery power level is a second value greaterthan the first value (e.g., the predefined mapping may map lowerremaining battery power levels to more power-efficient modulationschemes). In another example, scheduler 18310 may be configured toselect a more power-efficient modulation scheme when a power-saving modeindicator specifies that a power-saving mode is enabled than when thepower-saving mode indicator specifies that the power-saving mode is notenabled (e.g., the predefined mapping may map power-saving modes withhigher targeted power savings to more power-efficient modulationschemes). In another example, scheduler 18310 may be configured toselect a more power-efficient modulation scheme when an estimatedbattery power usage is a first value than when the estimated batterypower usage is a second value less than the first value (e.g., thepredefined mapping may map higher estimated battery power usages to morepower-efficient modulation schemes). In another example, scheduler 18310may be configured to select a more power-efficient modulation scheme(e.g., a lower-order modulation scheme) when a link quality metric(e.g., an SNR) is a first value than when the link quality metric is asecond value that is greater than the first value (e.g., the predefinedmapping may map lower link quality metrics to more power-efficientmodulation schemes).

In another example, scheduler 18310 may be configured to select a morepower-efficient modulation scheme when a distance (between terminaldevice 18202 and network access node 18204) is a first distance thanwhen the distance is a second distance that is less than the firstdistance (e.g., the predefined mapping may map higher distances to morepower-efficient modulation schemes). For example, when terminal device18202 is located further from network access node 18204, terminal device18202 may be able to reach network access node 17384 when terminaldevice 18202 uses a higher transmit power. However, using a highertransmit power may lead to more battery usage, and may therefore depletethe battery of terminal device 18202. When high transmit power is usedconcurrently with a less power-efficient modulation scheme, terminaldevice 18202 may experience considerable battery depletion. Accordingly,by selecting a more power-efficient modulation scheme for terminaldevice 18202 when it is located further from network access node 18204,scheduler 18310 may help terminal device 18202 to reduce power usage andextend battery life. In some aspects, scheduler 18310 may use a linkquality metric, such as SNR, in the same manner. For example, conditionswith low SNRs (for the radio access channel between terminal device18202 and network access node 18204) may warrant higher uplink transmitpowers by terminal device 18202 (e.g., similar to increasing distance).Accordingly, scheduler 18310 may be configured to select a morepower-efficient modulation scheme when a link quality metric (betweenterminal device 18202 and network access node 18204) is a first valuethan when the distance is a second value that is greater than the firstdistance (e.g., the predefined mapping may map lower SNRs to morepower-efficient modulation schemes).

In another example, scheduler 18310 may be configured to select a morepower-efficient modulation scheme when a temperature measurement (ofterminal device 18202) is a first value than when the temperaturemeasurement is a second value less than the first value (e.g., thepredefined mapping may map higher temperature measurement to morepower-efficient modulation schemes). For example, use of lesspower-efficient modulation schemes by terminal device 18202 can increaseits temperature, which can damage terminal device 18202 if high enough.Accordingly, scheduler 18310 may be configured to select morepower-efficient modulation schemes for terminal device 18202 when itstemperature is high. This can in turn help terminal device 18202 tomanage its temperature and avoid damaging high temperatures.

In another example, scheduler 18310 may be configured to select a morepower-efficient modulation scheme when a charging status of terminaldevice 18202 indicates that the battery power supply is not chargingthan when the charging status of terminal device 18202 indicates thatthe battery power supply is charging (e.g., the predefined mapping maymap enabled charging statuses to less power-efficient modulationschemes). In one exemplary scenario, terminal device 18202 may be at lowpower (e.g., 10% remaining battery power level), for which scheduler18310 would normally trigger a switch to a lower-order modulation scheme(e.g., from 16-QAM to QPSK). However, if terminal device 18202 iscurrently charging its battery power supply, there may not be a need toswitch to a lower-order/more power-efficient modulation scheme.Accordingly, scheduler 18310 may determine not to switch to thelower-order modulation scheme as the charging status indicates thatterminal device 18202 is charging. As remaining at the higher-ordermodulation scheme may slow the charging rate, this can be viewed as atradeoff between higher throughput versus faster battery power chargingrate.

In another example, scheduler 18310 may be configured to selectmodulation schemes based on the power amplifier characteristics in thebattery power status report. For example, the power amplifiercharacteristics may indicate that the PAE of the power amplifierterminal device 18202 when operating with different modulation schemes(e.g., where lower-order modulation schemes may yield higher PAEs thanhigher-order modulation schemes). The power amplifier characteristicsmay also indicate the PAE of the power amplifier of terminal device18202 at different frequencies (e.g., where operation at higherfrequencies may yield lower PAE). Scheduler 18310 may therefore usethese power amplifier characteristics to select the modulation schemefor terminal device 18202.

In another example, scheduler 18310 may be configured to select a morepower-efficient modulation scheme when a data rate demand (of a datastream that terminal device 18202 is transmitting) is a first value thanwhen the data rate demand is a second value greater than the first value(e.g., the predefined mapping may map higher data rate demands to lesspower-efficient modulation schemes). As less power-efficient modulationschemes are higher-order modulation schemes, less power-efficientmodulation schemes may be able to support higher data rates than morepower-efficient modulation schemes. If the data stream is rate-sensitive(e.g., has a higher data rate demand), scheduler 18310 may be configuredto select a less power-efficient modulation scheme that can providesufficient modulation order to support transfer of the data stream.

In some aspects, scheduler 18310 (and the predefined mapping) may selectthe modulation scheme in stage 18510 based on multiple control variables(e.g., using a multi-dimensional lookup table or a similar predefinedmapping that maps values for multiple control variables to a singlemodulation scheme). These examples therefore reflect the generalcorrespondence between high and low values of each control variable andwhether the resulting selected modulation scheme is more or lesspower-efficient.

After selecting the modulation scheme in stage 18510, scheduler 18310may generate a modulation scheme assignment message in stage 18512 thatspecifies the modulation scheme selected in stage 18510. Scheduler 18310may then transmit the modulation scheme to terminal device 18202 instage 18514 using transmitter 18304. Terminal device 18202 may thenreceive and read the modulation scheme assignment message to identifythe modulation scheme. Terminal device 18310 may then transmit tonetwork access node 18204 using the modulation scheme in stage 18516.

As previously indicated, the control variables can include data rateparameters and spectrum offload information of terminal device 18202.Scheduler 18310 can therefore in some aspects assign a modulation schemeto terminal device 18202 accompanied by an instruction to use spectrumoffload. For example, when scheduler 18310 assigns a morepower-efficient modulation scheme to terminal device 18202, this canreduce the data rate of the radio access channel between terminal device18202 and network access node 18204 (e.g., as the more power-efficientmodulation scheme may have lower-order, and thus not be able to encodeas much data into each modulation symbol). In some cases, the datastream that terminal device 18202 is transmitting may have data ratedemands that are higher than the supported data rate of the radio accesschannel when using the selected modulation scheme.

Accordingly, in such cases scheduler 18310 can be configured to assign amore-power efficient modulation scheme to terminal device 18202 alongwith an instruction to establish a second radio access channel on secondspectrum with spectrum offload. For example, terminal device 18202 mayinitially be transmitting the data stream to network access node 18204on a first radio access channel on first spectrum. Per the assignment byscheduler 18310 to use spectrum offload, terminal device 18202 mayestablish a second radio access channel on second spectrum with networkaccess node 18202. Terminal device 18202 may then split the data streaminto a first part and a second part, and to transmit the first part onthe first spectrum and to transmit the second part on the secondspectrum. The added bandwidth introduced by the second radio accesschannel may therefore enable terminal device 18202 to transmit the datastream with a sufficient data rate to continue to meet its data ratedemands. In some aspects, the second spectrum may be shared orunlicensed spectrum (e.g., on the unlicensed 60 GHz mmWave band or on anISM band) while the first spectrum may be on licensed spectrum (e.g., ona licensed LTE or 5G NR or mmWave band, e.g., the 28 GHz band=24-33 GHz,or the 39 GHz band=37-43.3 GHZ and even up to 45 GHz).

FIG. 186 shows an exemplary procedure according to some aspects thatscheduler 18310 can use as part of stage 18510 when considering theavailability of spectrum offloading at terminal device 18202. Aspreviously indicated, scheduler 18310 may collect the control variablesin stage 18508, where the control variables may include data rateparameters and spectrum offload information for terminal device 18202.Accordingly, in stage 18510 a scheduler 18310 may determine whetherspectrum offload is supported by terminal device 18202. For example, thespectrum offload information may specify whether terminal device 18202supports spectrum offloading (e.g., whether terminal device 18202 cansupport multiple radio access channels on different spectrum). In somecases, the spectrum offload information may specify which spectrumterminal device 18202 can perform spectrum offload on (e.g., which bandsterminal device 18202 can use for spectrum offload) and/or the amount ofspectrum that terminal device 18202 can perform spectrum offload with ona potential second radio access channel.

If scheduler 18310 determines that spectrum offload is supported byterminal device 18310, scheduler 18310 may proceed to stage 18510 b. Asspectrum offload is available, scheduler 18310 may be select a firstmodulation scheme for terminal device 18202 and generate an instructionfor terminal device 18202 to use the first modulation scheme withspectrum offload.

In some aspects, scheduler 18310 may select the first modulation schemeand generate the instruction for spectrum offload based on a data rateparameter included in the control variables. For example, the data rateparameter may indicate a data rate demand of the data stream beingtransmitted by terminal device 18202 on the first radio access channelto network access node 18204.

In some aspects, scheduler 18310 may first determine an overallbandwidth available to terminal device 18202 when using spectrumoffload. This can be based on the relations between frequency,bandwidth, and modulation scheme (e.g., where frequency is inverselyproportional to PAE, bandwidth and modulation scheme are directlyproportional to data rate, and modulation scheme order is inverselyproportional to PAE). As previously indicated, the spectrum offloadinformation may indicate an amount of spectrum that terminal device18202 can perform spectrum offload with on a potential second radioaccess channel, and scheduler 18310 can therefore determine the overallbandwidth of the first radio access channel and the potential secondradio access channel. Based on the overall bandwidth, scheduler 18310may select a modulation scheme (as the first modulation scheme) thatwould achieve at least the data rate demand of the data stream when usedfor the first and second radio access channels. In some aspects,scheduler 18310 may be configured to select the most power-efficientmodulation scheme (as the first modulation scheme) that would alsoachieve at least the data rate demand of the data stream when used forthe first and second radio access channels. Accordingly, scheduler 18310may be able to select a power-efficient modulation scheme for terminaldevice 18202 that would still enable terminal device 18202 to transmitthe data stream when used with spectrum offload. Even though thepower-efficient modulation scheme may have a lower data rate, theintroduction of the second radio access channel may provide addedbandwidth that can compensate for the lower data rate.

After selecting the first modulation scheme, scheduler 18310 may alsogenerate an instruction for spectrum offload that instructs terminaldevice 18202 to use the second spectrum to establish the second radioaccess channel. Scheduler 18310 may then proceed to stage 18512, wherescheduler 18310 may generate a modulation scheme assignment message thatidentifies the first modulation scheme. Scheduler 18310 may include theinstruction for spectrum offload in the modulation scheme assignmentmessage. Scheduler 18310 may then transmit the modulation schemeassignment message with transmitter 18304 to terminal device 18202 instage 18514. Terminal device 18202 may then read the modulation schemeassignment message and identify the first modulation scheme and theinstruction to perform spectrum offload. Terminal device 18202 may thenbegin transmitting using the first modulation scheme with spectrumoffload in stage 18516. For example, terminal device 18202 may beconfigured to split the data stream into first and second parts,modulate the first part with the first modulation scheme and transmitthe modulated first part on the first radio access channel on the firstspectrum, and modulate the second part with the second modulation schemeand transmit the modulated second part on the second radio accesschannel on the second spectrum. Terminal device 18202 may, for example,use any feature of spectrum offload described above for FIGS. 170-180 .Accordingly, even if the first modulation scheme is lower-order (e.g.,lower data rate) than a modulation scheme which terminal device 18202was previously using, terminal device 18202 may still transmit the datastream while meeting its data rate demands by using spectrum offload. Asthe first modulation scheme may be more power-efficient than theprevious modulation scheme, terminal device 18202 may be able to reducepower usage at its power amplifier and thus conserve battery power.

With reference to FIG. 186 , if scheduler 18310 determines that terminaldevice 18310 does not support spectrum offload in stage 18510 a,scheduler 18310 may proceed to stage 18510 c. As terminal device 18202may in some cases not have the option of adding bandwidth byestablishing a second radio access channel with second spectrum,scheduler 18310 may in some cases not be able to assign the firstmodulation scheme to terminal device 18202 (e.g., as the firstmodulation scheme has lower-order). In some aspects, scheduler 18310 mayselect the most power-efficient modulation scheme that still achievesthe data rate demands of the data stream when used for the first radioaccess channel (e.g., as no second radio access channel is available) instage 18510 c. As only the first radio access channel can be used totransmit the data stream, the second modulation scheme may havehigher-order than the first modulation scheme. As the second modulationscheme is higher-order than the first modulation scheme, it may also beless power-efficient. After selecting the second modulation scheme,scheduler 18310 may proceed to stage 18512 to generate the modulationscheme assignment message that identifies the second modulation scheme.Scheduler 18310 may then transmit the modulation scheme assignmentmessage to terminal device 18202 in stage 18514, after which terminaldevice 18202 may transmit the data stream using the second modulationscheme in stage 18516.

Application of spectrum offload by terminal device 18202 may thereforeenable scheduler 18310 to select more power-efficient modulation schemeseven when the data stream has data rate demands. This can help conservebattery power at terminal device 18202, as the use of morepower-efficient modulation schemes can help reduce the power usage byits power amplifier.

In some aspects, scheduler 18310 may collect and consider other controlvariables as part of the modulation scheme selection function in stages18508-18512. For example, in various aspects, scheduler 18310 may beconfigured to use control variables including any of: a manufacturer ofterminal device 18202, a model of terminal device 18202, anidentification of one or more components of terminal device 18202, oneor more frequency bands supported by terminal device 18202, one or moremodulation schemes supported by terminal device 18202, power amplifiercharacteristics of a power amplifier of terminal device 18202 atdifferent frequencies, power amplifier characteristics of a poweramplifier of terminal device 18202 at different modulation schemes, oneor more radio access communication technologies supported by terminaldevice 18202, a movement direction of terminal device 18202, a movementspeed of terminal device 18202, an elevation of terminal device 18202, adestination of terminal device 18202, a point of interest (POI) toterminal device 18202, an estimated time before terminal device 18202leaves the coverage area of network access node 18204 information aboutnetwork access node 18204, information about a network that networkaccess node 18202 is part of, information about a connection of terminaldevice 18202, user input information, information about an applicationof terminal device 18202, a manufacturer of one or more components ofnetwork access node 18204, a model of one or more components of networkaccess node 18204, one or more frequency bands supported by networkaccess node 18204, one or more modulation schemes supported by networkaccess node 18204, one or more radio access technologies supported bynetwork access node 18204, capacity information of network access node18204, information about one or more power resources of network accessnode 18204, CSI feedback information for terminal device 18202, areceived signal strength indicator (RSSI), a reference signal receivepower (RSRP), a reference signal receive quality (RSRQ), a channelquality indicator (CQI), a packet loss rate (PLR), a bit error rate(BER), a block error rate (BLER), signal to noise ratio (SNR), adownlink throughput, an uplink throughput, a signal to noise ratio(S/N), a carrier to noise ratio (C/N), an interference to noise ratio(CI/N), a handover duration, a handover success rate, minutes of userper dropped call (MOU), and/or other key performance indicators (KPIs),a type of connection of terminal device 18202, a link quality of theconnection, a throughput of the connection, a latency of the connection,a redundancy of the connection, and/or one or more target serviceparameters of terminal device 18202 (e.g., a target latency, a targetdata throughput, and/or a target error rate). Any one or more of thesecontrol variables may be implemented as part of the predefined mapping,where the predefined mapping may output different modulation schemesbased on their value.

In one specific example, scheduler 18310 may base selection of a secondmodulation scheme for terminal device 18202 on transmission power (e.g.,an estimated transmission power based on a distance or a link qualitymetric), battery power status, power amplifier characteristics, and anestimated duration of data exchange (e.g., based on the length of thedata stream being transmitted by terminal device 18202). Scheduler 18310may therefore obtain these control variables and, for example, apply apredefined mapping to select a second modulation scheme for terminaldevice 18202 (e.g., where the predefined mapping maps different valuesof each of these control variables to different modulation schemes).

Various aspects described above reference a modulation scheme selectionfunction for a single terminal device. In some aspects, scheduler 18310may also be configured to apply the modulation scheme selection functionto select modulation schemes for a plurality of terminal devices. FIG.187 shows an example according to some aspects, where network accessnode 18204 may be serving terminal device 18202 in addition to terminaldevices 18702-18704. Scheduler 18310 of network access node 18204 maytherefore be configured to select respective modulation schemes for eachof terminal devices 18202, 18702, and 18704.

In some aspects, scheduler 18310 may be configured to select therespective modulation scheme for each of terminal devices 18202, 18702,and 18704 in an independent manner. For example, scheduler 18310 maycollect different sets of control variables for each of terminal devices18202, 18702, and 18704, and separately apply the procedure of messagesequence chart 18400 or 18500 to select respective modulation schemesfor terminal devices 18202, 18702, and 18704 based on their respectivesets of control variables.

In other aspects, scheduler 18310 may be configured to select therespective modulation schemes for terminal devices 18202, 18702, and18704 (e.g., for multiple terminal devices) in a combined procedure.FIG. 188 shows exemplary message sequence chart 18800 according to someaspects, which describes a modulation scheme selection function appliedto multiple terminal devices. As shown in FIG. 188 , terminal devices18202, 18702, and 18704 may each send a battery power status report(e.g., indicating their own respective battery power status) and/oradditional control variable reports in stages 18804-18806. Networkaccess node 18204 may then collect the control variables in stage 18808.

Then, scheduler 18310 may select respective modulation schemes forterminal devices 18202, 18702, and 18704 based on the control variablesin stage 18810. Instead of independently determining a modulation schemefor each of terminal devices 18202, 18702, and 18704 based on theirrespective control variables, scheduler 18310 may concurrently considerthe impact of assigning various modulation schemes to terminal devices18202, 18702, and 18704. For example, scheduler 18310 may treat theassignment of modulation schemes to terminal devices 18202, 18702, and18704 as the distribution of a fixed set of resources amongst aplurality of terminal devices. As there may be a fixed set of resourcesthat can be distributed, scheduler 18310 may select the modulationscheme for a given terminal device based on the modulation schemesassigned to other terminal devices. The number of terminal devices towhich scheduler 18310 assigns modulation schemes can be scalable to anynumber.

Scheduler 18310 may then in stage 18812 generate respective modulationscheme assignment messages for each of terminal devices 18202, 18702,and 18704 that identify the modulation schemes respectively selected forterminal devices 18202, 18702, and 18704. Scheduler 18310 may then sendthe modulation scheme assignment messages to terminal devices 18202,18702, and 18704 with transmitter 19204 in stage 18814. Terminal devices18202, 18702, and 18704 may then each transmit using their respectivelyassigned modulation schemes in stage 18816.

Various aspects described above include scheduler 18310 (and itsmodulation scheme selection function) as part of a network access node.In other aspects, scheduler 18310 may be deployed as part of a corenetwork server that interfaces with network access node 18204. Forexample, with reference to FIG. 183 , scheduler 18310 may be located inthe core network, and may provide modulation scheme assignment messagesto network access node 18204 for network access node 18204 to transmitto terminal device 18202.

In some aspects, the modulation scheme selection function may beimplemented in a terminal device, such as terminal device 18202. Forinstance, using the example where terminal device 18202 is configured inthe manner of terminal device 102 as in FIG. 2 , protocol controller 210may be configured to select a modulation scheme based on controlvariables, and to send a request to network access node 18204 to use themodulation scheme via transceiver 204. Terminal device 18202 may then beconfigured to use the modulation scheme if network access node 18204accepts the request.

FIG. 189 shows exemplary message sequence chart 18900 according to someaspects, which shows one such example where terminal device 18202executes the modulation scheme selection function. As in the case ofFIGS. 184, 185 , and 188, the selection function may use the batterypower status of terminal device 18202 as a control variable. Terminaldevice 18202 may therefore determine its battery power status in stage18902. For example, application processor 212 of terminal device 18202may report a remaining battery power level and/or a power-saving modeindicator to protocol controller 210. Protocol controller 210 may thenuse this battery power status as a control variable.

In some aspects, protocol controller 210 may also collect other controlvariables in stage 18904. For example, protocol controller 210 maydetermine or estimate a distance between terminal device 18202 andnetwork access node 18204 (e.g., using a current position of terminaldevice 18202 and the position of network access node 18204, or byestimating the distance with a signal strength measurement by digitalsignal processor 208), and use this distance as a control variable. Invarious other examples, protocol controller 210 may collect any of atemperature of terminal device 18202, charging status of terminal device18202, power amplifier characteristics of a power amplifier of terminaldevice 18202, data rate demands, and/or spectrum offload information forterminal device 18202 as control variables in stage 18904.

Protocol controller 210 may then select a modulation scheme based on thecontrol variables in stage 18906. For example, as previously describedabove for stages 18406 of FIG. 184 and stage 18510 of FIG. 185 ,protocol controller 210 may be configured to use a predefined mapping(e.g., a lookup table) or other selection logic (e.g., a modulationscheme selection equation) to select a modulation scheme based on thecontrol variables. Protocol controller 210 may therefore use anyfunctionality described above to select the modulation scheme based onthe control variables in stage 18906. In various examples, protocolcontroller 210 may be configured to select more power-efficientmodulation schemes when the remaining battery power level is lower, whenthe power-saving mode indicator is enabled, when the distance is larger,and/or when the temperature is higher. In some aspects, it may beadvantageous for the modulation scheme selection function to be executedat terminal device 18202 to select modulation schemes based ontemperature, as temperature fluctuations may be rapid and the latencyinvolved in executing the modulation scheme selection function atnetwork access node 18204 may be too high.

Protocol controller 210 may then generate a modulation scheme requestmessage in stage 18908, and may send the modulation scheme requestmessage to network access node 18204 via transceiver 204. Scheduler18310 of network access node 18204 may receive and read the modulationscheme request message, and may determine whether to accept or rejectthe modulation scheme request message. In the example of FIG. 189 ,scheduler 18310 may accept the modulation scheme request message (e.g.,may accept the request by terminal device 18202 to use the modulationscheme), and may therefore send a modulation scheme accept message toterminal device 18202 in stage 18912.

Protocol controller 210 may receive and read the modulation schemeaccept message, and may therefore determine that network access node18204 has accepted the modulation scheme request message. Protocolcontroller 210 may then control digital signal processor 208 of terminaldevice 18202 to transmit using the modulation scheme in stage 18914.

In one example of message sequence chart 18900, protocol controller 210may be configured to compare a remaining battery power level of terminaldevice 18202 to a threshold as part of stage 18906, and to select amodulation scheme based on whether the remaining battery power level isless than the threshold. For example, the threshold can be predetermined(e.g., a predetermined remaining battery power level that indicates lowpower, such as 10%, 20%, etc.), or can be user-determined (e.g., auser-selected remaining battery power level that indicates low power).If protocol controller 210 determines that the remaining battery levelis less than the threshold in stage 18906, protocol controller 210 maybe configured to select a more power-efficient modulation scheme torequest in stage 18906. For example, if terminal device 18202 isinitially using a QAM scheme, such as 16-QAM, 32-QAM, or 64-QAM,protocol controller 210 may select a PSK modulation scheme if theremaining battery power level is below the threshold, such as QPSK orBPSK. This can therefore help reduce power consumption and extendbattery life at terminal device 18202 in scenarios where the remainingbattery power level is low (e.g., less than the threshold).

In another example, protocol controller 210 may be configured todetermine whether a power-saving mode indicator is enabled or disabledin stage 18906. If the power-saving mode indicator is enabled (e.g.,meaning that the power-saving mode is on), protocol controller 210 maybe configured to select a more power-efficient modulation scheme torequest in stage 18906. For example, when protocol controller 210determines that the power-saving mode is enabled, protocol controller210 may switch from a QAM scheme to a PSK scheme. This can likewise helpreduce power consumption and extend battery life at terminal device18202 when the power-saving mode is enabled.

In some aspects, various examples described may also be implemented inthe downlink direction, such as where scheduler 18310 selects a downlinkmodulation scheme for network access node 18204 to use to transmit toterminal device 18202. Any example described above can therefore beimplemented with the power efficiency of the power amplifier of networkaccess node 18204 and/or the power usage of network access node 18204.This can be useful, for example, when the network operator of networkaccess node 18204 wishes to reduce power usage (e.g., to reduce costs),and/or when network access node 18204 is battery powered. For example,downlink modulation scheme selection function can be executed atscheduler 18310 when network access node 18204 is a temporary basestation or access node deployed by a drone or balloon, a network accessnode deployed in the field for emergency purposes when grid power isunavailable, or a network access node deployed to increase connectivityat venues or events in stadiums were pre-existing network access nodesare insufficient to handle the temporary surge in connectivity demands.

FIG. 190 shows exemplary method 19000 of operating a network access nodeaccording to some aspects. As shown in FIG. 190 , method 19000 includesobtaining a battery power status for a terminal device with a firstmodulation scheme (19002), selecting a second modulation scheme for theterminal device if the battery power status meets a predefined condition(19004), and sending a modulation scheme assignment message to theterminal device that identifies the second modulation scheme (19006).

FIG. 191 shows exemplary method 19100 operating a terminal deviceaccording to some aspects. As shown in FIG. 191 , method 19100 includesdetermining a battery power status of the terminal device while theterminal device is assigned a first modulation scheme (19102), selectinga second modulation scheme for the terminal device if the battery powerstatus meets a predefined condition (19104), and sending a modulationscheme request message to a network access node that requests assignmentof the second modulation scheme to the terminal device (19106).

FIG. 192 shows exemplary method 19200 of operating a network access nodeaccording to some aspects. As shown in FIG. 192 , method 19200 includesobtaining a plurality of control variables for a terminal device with afirst modulation scheme (19202), selecting a second modulation schemebased on a predefined mapping that maps control variables to modulationschemes (19204), wherein the one or more control variables include abattery power status, and sending a modulation scheme assignment messageidentifying the second modulation scheme to the terminal device (19206).

Configurable, Self-Calibrating and Self Correcting Baseband Modem

Vehicular communication devices and terminal device platforms may facedistinct challenges due to their respective differences. One suchdifference arises from the arrangement of one or more components withina vehicular communication device, such as vehicular communication device500. In at least one aspect, one or more components may be embeddedwithin vehicular communication device 500. For instance, one orcomponents may be embedded within the vehicular housing of vehiclecommunication device 500, near the window(s) and/or outside of thevehicular housing for increased radio frequency (RF) sensitivity. Theplacement of one or more components of vehicular communication device500 may thus contribute to the difficulty in performing service onvehicular communication device 500. It would thus be beneficial toprovide a non-invasive solution to service vehicular communicationdevices without damage thereto.

Another difference stems from the life cycle of a vehicularcommunication device, which may be designed to outlast that of aterminal device platform. In view of this consideration, vehicularcommunication devices may benefit from a more flexible design. In someaspects, V2X technology may be based on one or more communicationprotocols (e.g., 3GPP LTE). While both vehicular communication devicesand terminal device platforms may benefit from upgrades as additionaltechnological advances are introduced, the number of upgrades is likelyto be greater for vehicular communication devices in view of theirexpected life cycles.

In light of these factors, auto manufacturers and the auto industry arefaced with the task of determining the best way to upgrade vehicularcommunication devices without waiting for individuals to bring theirvehicular communication devices in for service and without damage totheir vehicular communication devices.

In some aspects, one or more components may be disposed (e.g., built)into a serviceable position of vehicular communication device 500 toaddress issues relating its location. According to at least one aspect,the serviceable position of the vehicular communication device 500 maybe visible or hidden. One or more trim pieces may, in some aspects, beadded to protect a portion of vehicle communication device 500. Forfurther protection, a panel or cover may also be included to protectand/or hide at least a portion vehicle communication device 500 inaccordance with at least one aspect.

One or more components of terminal device 102 or vehicular communicationdevice 500 may, in some aspects, be added, removed and/or replaced tofacilitate maintenance. According to at least one aspect, a component ofterminal device 102 and/or vehicular communication device 500 mayinclude hardware, software, or some combination thereof. When acomponent, for instance, stops working as intended, is no longerdesired, and/or becomes outdated, for example, it may be removed orreplaced with one or more components. By providing a mechanism forinterchanging components, various hardware and/or softwarefunctionalities may be integrated into terminal device 102 and/orvehicular communication device 500.

Despite the ability to service terminal device 102 and/or vehicularcommunication device 500 without damage thereto, owners may be taskedwith the inconvenience of bringing their terminal device 102 and/orvehicular communication device 500 in for service.

As provided herein, a wireless baseband modem of terminal device 102and/or vehicular communication device 500 may, in some aspects,diagnose, calibrate performance, and/or obtain one or more componentstherein or functionalities thereof. According to at least one aspect,the wireless baseband modem may be re-configured with new radiocommunication technologies by virtue of an over-the-air (OTA) update.

In some aspects, anan OTA update may be used for distributing data overan air interface to update one or more target devices. According to atleast one aspect, the target device may be terminal device 102, and/or avehicular communication device 500, for example. This data may, in someaspects, include one or more parameters, data structures, tables,libraries, threads, instructions, sub-routines, procedures, functions,routines, applications, software, operating systems and/or anyportion(s) thereof, for example. Additional features may thus beintroduced for integration with the vehicle itself or vehicularcommunication device.

By providing a mechanism for calibration and correction, owners mayreduce the frequency of bringing their terminal devices and/or vehicularcommunication device into a service facility for support. Furthermore,terminal devices and/or vehicular communication devices may beconfigured to download at least a portion of support for new radiocommunication technologies and/or various types of value-added features.

FIG. 193 shows an exemplary internal configuration of radiocommunication arrangement 504 and antenna system 506 of a vehicularcommunication device 500 according to some aspects. As shown in FIG. 193, radio communication arrangement 504 may include a baseband integratedcircuit 19302, a baseband RF integrated interface circuit 19304, RFintegrated circuit 19306, RF integrated circuit 19308, envelope tracking(ET) integrated circuit 19310, ET integrated circuit 19312, LNA bank19314, LNA bank 19316, PA integrated circuit 19318, PA integratedcircuit 19320, duplexer 19322, and duplexer 19324. Although a basebandintegrated circuit 19302, a baseband RF integrated interface circuit19304, RF integrated circuit 19306, RF integrated circuit 19308, ETintegrated circuit 19310, ET integrated circuit 19312, LNA bank 19314,LNA bank 19316, PA integrated circuit 19318, PA integrated circuit19320, duplexer 19322, and duplexer 19324 are illustrated in radiocommunication arrangement 504, some aspects may employ additional orfewer baseband integrated circuits, baseband RF integrated circuits, RFintegrated circuits, ET integrated circuits, LNA banks, PA integratedcircuits, duplexers and/or other elements.

With continued reference to FIG. 193 , RF integrated circuit 19306 may,in some aspects, be configured for a first set of frequency bands,whereas RF integrated circuit 19308 may be configured for a second setof frequency bands. According to at least one aspect, the first set offrequency bands may be the same set of frequency bands as the second setof frequency bands. The first set of frequency bands may, in someaspects, be mutually exclusive from the second set of frequency bands.In at least one aspect, the first set of frequency bands may overlap, atleast in part, in frequency with the second set of frequency bands.

With continued reference to FIG. 193 , antenna system 506 may includeantenna tuner 19326. Although antenna tuner 19326 is illustrated inantenna system 506, some aspects may employ additional or fewer antennatuners and/or other elements. As previously described with respect toFIG. 6 , antenna system 506 may also include a single antenna, anantenna array that includes multiple antennas, an analog antennacombination and/or beamforming circuitry.

The performance of one or more components within vehicular communicationdevice 500 may change over time. In some aspects, the performance of oneor more components of vehicular communication device 500 may degradebased on a variety of factors. According to at least one aspect, thesefactors may include may include a mechanical condition of one or morecomponents of vehicular communication device 500, an electricalcondition of one or more components of vehicular communication device500, an environmental condition of one or more components of vehicularcommunication device 500, and/or a state condition of one or morecomponents of vehicular communication device 500, for example.

In some aspects, one or more components of vehicular communicationdevice 500 may result in a degradation in performance, a faultoccurrence and/or a failure based on one or more of these factors.

A mechanical condition of one or more components of vehicularcommunication device 500 may, in some aspects, be based on a compressionload, a tension load, a shear load, a bending load and/or a torsionload, for example.

In some aspects, an electrical condition of one or more components ofvehicular communication device 500 may be based on an overcurrent, anovervoltage, an undervoltage, an overcurrent, an undercurrent, a shortcircuit, an open circuit, a reverse bias, an electromagnetic force (EMF)and/or an electrostatic discharge (ESD), for example.

An environmental condition of one or more components of vehicularcommunication device 500 may, in some aspects, be based on a chemicalreaction (e.g., corrosion), a temperature, a barometric pressure, apresence of a gas, a presence of a vapor, and/or a presence of liquid,for example.

In some aspects, a state condition of the one or more components ofvehicular communication device 500 may be based on an active condition,an “ON” condition, a passive condition, an “OFF” condition, an errorcondition, a resource utilization, and/or a quiescent condition, forexample.

A component of terminal device 102 and/or vehicular communication device500 may, in some aspects, include hardware, software, or somecombination thereof. In some aspects, a component of a vehicularcommunication device may include a processor, a processor core, amicroprocessor, an integrated circuit, a controller, a FPGA, a clock, anoscillator (e.g., crystal), an LNA, a PA, a baseband modem, tuner, RFfront end, a memory, an interface, a switch, and/or a software-definedradio (SDR) component implemented as a processor to executesoftware-defined instructions, for example, or any portion(s) thereof.

In some aspects, one or more components of terminal device 102 and/orvehicular communication device 500 may include one or more algorithms tocompensate for one or more of the factors listed above. According to atleast one aspect, some built-in calibration and automatic correctionmethods may not adequately alleviate the quantity and/or extent offactors encountered for the duration for which the components ofterminal device 102 and/or vehicular communication device 500 aredesigned.

While certain aspects are specifically described herein in the contextof a vehicular communication device 500, it should be noted that aterminal device 102 and a terminal device implemented 102 as a vehicularcommunication device 500 may face some similar challenges due tooverlapping design constraints. For instance, one or more components ofa vehicular communication device 500 may, in some aspects, be configuredin accordance with one or more communication protocols of radiocommunication network 100. According to at least one aspect, the numberof external RF font end components in a cellular modem of a vehicularcommunication device 500 may increase with respect to the number offrequency bands supported by the radio communication network 100. Inthis regard, a TX feedback receiver may, in some aspects, be addedwithin the cellular modem to communicate in accordance with one or morecommunication protocols of the radio communication network 100. In atleast one aspect, the additional TX feedback receiver may be configuredto perform closed loop power control to achieve a power ramping timewithin 1 ms (70 μs for LTS sounding reference signals (SRS)). While thepreceding example is merely illustrative in nature, the added hardwarecomplexity may contribute to the effect of aging on one or morecomponents of a vehicular communication device 500. Accordingly,conventional diagnostics performed on vehicular communication device 500or even terminal device 102 may be insufficient in detecting theeffect(s) of aging because such diagnostics occur prior to massdeployment.

In view of the foregoing, providing a framework for in-fielddiagnostics, in-field calibration, and/or OTA updates may be beneficial.In some aspects, an in-field diagnostic process may detect one or moreissues (e.g., hardware, software, hardware and/or software, amongothers) within a terminal device 102. A detected issue may, forinstance, be attributable to one or more components of a terminal device102, such as a failing RF front-end component, a drift in the clock of alocal frequency oscillator, for example. According to at least oneaspect, an in-field calibration process and/or an OTA update may beperformed to compensate for an issue detected through the in-fielddiagnostic process. As a result, the added burden of, for instance,uninstalling a component and sending it back to the factory can beavoided.

Terminal device 102 and/or vehicular communication device 500 may beconfigured to interface with one or more devices for in-fielddiagnostics, in-field calibration, and/or OTA update. FIG. 194 shows anexemplary configuration in accordance with some aspects where terminaldevice 102 interface with one or more devices 19400. As shown in FIG.194 , for instance, terminal device 102 may be configured to communicatewith network access node 110, terminal device 104, and/or itself.Although terminal device 102 may interface with network access node 110,terminal device 104, and/or itself as shown in FIG. 194 , some aspectsmay employ additional or fewer interfaces with network access nodes,terminal devices, and/or other devices. Although terminal device 102 isillustrated in FIG. 194 , terminal device 102 may, for instance, beimplemented as vehicular communication device 500.

In some aspects, the one or more devices 19400 may include a terminaldevice, a vehicular communication device, a network access node, acore-network entity, an authentication entity, an Internet of Things (I)device, a road side unit (RSU), a drone, an IoT fuel pump, anelectric-vehicle charging station, automotive service/repair stationequipment, and/or network service provider equipment, among others.According to at least one aspect, the one or more devices 19400 may beincluded in the radio communication network 100. Additionally oralternatively, the one or more devices 19400 may be included on anexternal data network. As further described herein, the one or moredevices 19400 may, in some aspects, be “certified” to facilitatein-field diagnostics and/or in-field compensatory measures.

Terminal device 102 and the one or more devices 19400 may, in someaspects, be configured to communicate via one or more of the radiocommunication technologies described herein. According to at least oneaspect, terminal device 102 may be configured to communicate withnetwork access node 110 through interface 19402. Interface 19402 may,for instance, include an uplink communication channel and/or a downlinkcommunication channel. In some aspects, terminal device 102 may beconfigured to communicate with terminal device 104 through interface19404. Interface 19404 may, for example, include a peer-to-peercommunication link, such as 3GPP sidelink based D2D, V2V communications,Bluetooth, Bluetooth Low Energy (BTLE), WiFi Direct, among others.

Terminal device 102 may, in some aspects, be configured to communicatewith itself via interface 19406. Interface 19406 may, for instance,include an internal TX-RX feedback path, an external feedback loop,among others. According to at least one aspect, the transmitter andreceiver of terminal device 102 may be configured to operate (e.g.,concurrently) on the same carrier frequency. By operating on the samefrequency, the transmitted signals may, in some aspects, be routed intothe receiver within the same hardware platform of terminal device 102.

With continued reference to FIG. 194 , an in-field diagnostic, in-fieldcalibration and/or an OTA update of terminal device 102 and/or vehicularcommunication device 500 may be performed without the inconvenience ofgoing to a service or repair facility. In some aspects, an in-fielddiagnostic, an in-field calibration, and/or an OTA update may beimplemented by executing one or more run-time processes. According to atleast one aspect, terminal device 102 may be configured to execute atleast a portion of an in-field diagnostic process, an in-fieldcalibration process, and/or an OTA update process of terminal device102. The one or more devices 19400 may, in some aspects, be configuredto facilitate at least a portion of the in-field diagnostic process, anin-field calibration process, and/or OTA update process of terminaldevice 102. In at least one aspect, terminal device 102 and the one ormore devices 19400 may be configured to collectively perform at least aportion of an in-field diagnostic process, an in-field calibrationprocess, and/or an OTA update process of terminal device 102, or anyportion(s) thereof.

In some aspects, an authentication procedure may be performed inaccordance with at least one of an in-diagnostic process, an in-fieldcalibration process, and/or an OTA update process. According to at leastone aspect, terminal device 102 and/or vehicular communication device500 may be configured to perform at least a portion of theauthentication procedure. One or more devices 19400 may, in someaspects, be configured to perform at least a portion of theauthentication procedure. In at least one aspect, the terminal device102 or vehicular communication device 500 may be configured tocollectively perform at least a portion of the authentication procedurewith the one or more devices 19400.

Authentication may, in some aspects, include the verification ofauthentication information. According to at least one aspect, theauthentication information may include a subscriber identityinformation, a certificate, a make of the terminal device, a model ofthe terminal device, a year of the terminal device, a color of thevehicular communication device, identification of one or moreaftermarket parts installed in the vehicular communication device, anidentity of the one or more devices, a version number of the data to besent to the vehicular communication device, and/or a version of the datastored on the vehicular communication device.

The timing at which authentication is performed may vary. In someaspects, authentication may be performed prior to an in-field diagnosticprocess, an in-field calibration process, and/or an OTA update process.According to at least one aspect, authentication may be performed afteran in-field diagnostic process, an in-field calibration process, and/oran OTA update process. Authentication may, in some aspects, be performedduring an in-field diagnostic process, an in-field calibration process,and/or an OTA update process.

In some aspects, an in-field diagnostic process, in-field calibrationprocess and/or an OTA update process of terminal device 102 and/orvehicular communication device 500 may be performed in an unsupervisedmode of operation and/or a supervised mode of operation. According to atleast one aspect, terminal device 102 may be configured to execute atleast a portion of in-field diagnostic process, and/or an in-fieldcalibration process in an unsupervised mode of operation. Terminaldevice 102 may, in some aspects, be configured to execute at least aportion of in-field diagnostic process, an in-field calibration process,and/or an OTA update process in a supervised mode of operation. In atleast one aspect, the one or more devices 19400 may be configured tofacilitate at least a portion of the in-field diagnostic process, anin-field calibration process, and/or OTA update process of terminaldevice 102 in a supervised mode of operation.

An unsupervised mode of operation may, in some aspects, be performedwithout the assistance of the one or more devices 19400. According to atleast one aspect, however, the unsupervised mode of operation mayinclude some form of communication with the one or more devices 19400.In some aspects, the terminal device 102 may be configured exchange oneor more messages with the radio communication network 100 in theunsupervised mode of operation concurrently with the in-field diagnosticprocess and/or an in-field calibration process of terminal device 102.In at least one aspect, the one or more messages may include, forinstance, a measurement report to a network access node 110 during anidle state connection therewith.

In some aspects, the supervised mode of operation may, for instance, beperformed with the assistance of the one or more devices 19400.According to at least one aspect, the one or more devices 19400 may beconfigured to control at least a portion of the in-field diagnosticprocess, an in-field calibration process, and/or an OTA update processof terminal device 102 in the supervised mode of operation. The one ormore devices 19400 may, in some aspects, be configured to issue one ormore instructions to terminal device 102 in the supervised mode ofoperation concurrently with the in-field diagnostic process, an in-fieldcalibration process of terminal device 102, and/or OTA update process.

An in-field diagnostic process, an in-field calibration process, and/orOTA update process of terminal device 102 and/or vehicular communicationdevice 500 may, in some aspects, be a software-defined radio (SDR)component implemented by one or more processors configured to at least aportion of execute software-defined instructions. Although certainaspects herein may describe an in-field diagnostic process, an in-fieldcalibration process and/or an OTA update process from the perspective ofa terminal device 102, the in-field diagnostic process, an in-fieldcalibration process, and/or an OTA update process or any portion(s)thereof, may be executed in the terminal device 102, vehicularcommunication device 500 and/or the one or more devices 19400,individually or collectively. In some aspects, one or more processors ofterminal device 102 (e.g., digital signal processor 208, controller 210,application processor 212, among others) and/or the one or more devices19400 (e.g., radio transceiver 304, physical layer processor 308,protocol controller 310, among others) may be configured to execute atleast a portion of the in-field diagnostic process, an in-fieldcalibration process, and/or an OTA update process of a device under test(e.g., terminal device 102, vehicular communication device 500, amongothers).

FIG. 195 shows an exemplary flow diagram 19500 for a device under test(e.g., terminal device 102, vehicular communication device 500, amongothers) according to some aspects. As shown in FIG. 195 , flow diagram19500 may begin with a determination as to whether one or more eventsare detected 19502. If it is determined that one or more events are notdetected, the process may restart. If, however, it is determined thatone or more events are detected, an in-field diagnostic process of thedevice under test may be performed 19504. After the in-field diagnosticprocess is completed, a result of the in-field diagnostic process may beanalyzed 19506. Upon analysis the result of the in-field diagnosticprocess 19506, it is determined as to whether one or morecountermeasures are to be performed 19508. If it is determined in theaffirmative, one or more countermeasures for the device under test maybe performed 19510. After performing the one or more countermeasures forthe device under test 19510, one or more countermeasures for the deviceunder test may be logged 19512. Upon logging the one or morecountermeasures of the device under test 19512, the process may restart.

As previously noted, flow diagram 19500 may begin with a determinationas to whether one or more events are detected 19502. In some aspects,this determination may provide for the detection of a variety of events.According to at least one aspect, the one or more events may include atemporal event, a performance event, a geographic event, a connectionevent, a power event, and/or a notification event, among others.

In some aspects, a temporal event may be based on a temporal value, acounter value, a clock value, a time of day, a temporal duration, aclock duration, a timer expiration, a countdown timer, a scheduled time,a random time, and/or an age of a device under test, among others, orany component or portion(s) thereof.

A performance event may, in some aspects, be based on a received signalstrength indicator (RSSI), a reference signal receive power (RSRP), areference signal receive quality (RSRQ), a channel quality indicator(COI), a packet loss rate (PLR), a bit error rate (BER), a block errorrate (BLER), signal to noise ratio (SINR), a downlink throughput, anuplink throughput, a signal to noise ratio (S/R), a carrier to noiseratio (C/N), an interference to noise ratio (C/N), a handover duration,a handover success rate, minutes of user per dropped call (MOU), and/orother key performance indicators (KPIs), among others.

In some aspects, a geographic event may be based on a location, aboundary, and/or proximity thereto, among others. According to at leastone aspect, a location may be based on a location of the device undertest (e.g., home), a location of where an in-field diagnostic for thedevice under test was previously performed (e.g., completed), a point ofinterest input by a user, and/or a proximity to the one or more devices19400. The location may, in some aspects, be based on a locationdetermined by a navigational system (e.g., global positioning system(GPS)), the device under test, and/or the one or more devices 19400. Inat least one aspect, the boundary may be a physical boundary, apolitical boundary, and/or any other type of boundary.

A connection event may, in some aspects, be based on a communicationconnection. In some aspects, a connection event may include anidentifier of an entity of the communication connection (e.g., a networkaccess node), a duration to synchronize to a known network access nodefor which synchronization was previously successful, a failure tosynchronize with a network access node for which synchronization waspreviously successful, a duration of an established communicationconnection, a type of communication connection, a link quality of anestablished communication connection, a throughput of an establishedcommunication connection, an identity of one or more entitiesparticipating in the communication connection, and/or a statusdesignation (e.g., cluster head) of one or more entities participatingin the communication connection. According to at least one aspect, adevice under test may be configured to determine an identifier of anetwork access node by a Cell ID and/or location information (e.g., GPScoordinates). The device under test may, in some aspects, be configuredto determine that a synchronization failure occurred in the absence ofdetecting a primary synchronization signal or secondary synchronizationsignal from a network access node (e.g., after a predeterminedduration).

In some aspects, a power event may be based on a power supply level, abackup power supply level, an amount of estimated battery time remainingin the device under test and/or the one or more devices 19400.

A notification event may, in some aspects, be based on a notificationfrom radio communication network 100, a notification from a manufacturerand/or another entity. According to at least one aspect, radiocommunication network 100 may determine data (e.g., an OTA update) isavailable for the device under test. In some aspects, the radiocommunication network 100 may match an identity of the device under testwith the data to be transmitted thereto.

In some aspects, the detection of one or more events may be performed invarious manners. According to at least one aspect, the device under testmay be configured to determine whether the one or more events aredetected. The one or more devices 19400 may, in some aspects, beconfigured to determine whether the one or more events are detected. Inat least one aspect, the device under test and the one or more devices19400 may be configured to collectively determine whether one or moreevents are detected.

In some aspects, the determination as to whether one or more events aredetected may include determining whether one or more events haveoccurred, are presently occurring, and/or are likely to occur in thefuture. According to at least one aspect, the one or more events may, insome aspects, be based on device under test and/or the one or moredevices 19400. The one or more events may, in some aspects, be based onwhether one or more events have occurred, are present occurring and/orare likely occur in the device under test. In at least one aspect, theone or more events may, in some aspects, be based on whether one or moreevents have occurred, are present occurring and/or are likely occur inthe one or more devices 19400.

According to at least one aspect, the device under test may beconfigured to determine whether the one or more events are detected. Theone or more devices 19400 may, in some aspects, be configured todetermine whether the one or more events are detected. In at least oneaspect, the device under test and the one or more devices 19400 may beconfigured to collectively determine whether one or more events aredetected.

With continued reference to FIG. 195 , in some aspects, the process mayrestart if it is determined that one or more events are not detected. Insome aspects, the determination as to whether one or more events aredetected may be performed at various times, such as periodically.According to at least some aspects, the determination as to whether oneor more events are detected may operate in a continuous manner. Thedetermination as to whether one or more events are detected may, in someaspects, be triggered upon one or more conditions (e.g., signaling fromthe radio communication network) being met.

With continued reference to FIG. 195 , in some aspects, a determinationthat one or more events are detected may trigger the performance of anin-field diagnostic process 19504 of the device under test. Although thedetermination that one or more events is detected are described totrigger the performance of an in-field diagnostic process, thisdetermination may trigger an in-field calibration process and/or an OTAupdate process in some aspects.

In some aspects, various forms of signaling may be utilized for anin-field diagnostics process. According to at least one aspect, the oneor more signals for the in-field diagnostics process may includeutilization of one or more reference signals. The one or more referencesignals may, in some aspects, be standardized signals and/ornon-standardized signals. In at least one aspect, the one or morereference signals may include one or more waveforms (e.g., sine wave,cosine wave, pulse wave, square wave, among others) in which theamplitude, phase, frequency, start and/or stop of the one or morereference signals may be varied over time. According to some aspects,the amplitude, phase, frequency, start and/or stop may be constant orvariable for a predetermined duration.

The one or more references signals may, in some aspects, include anencoded bit sequence which is known to the receiver. According to atleast one aspect, the one or more references signals may be transmittedon a specific resource block, which is known to the receiver. In someaspects, the specific resource block may be defined by a position intime and frequency. In at least one aspect, the receiver may beconfigured to measure one or more errors in the transmitted one or morereference signals.

In some aspects, various devices may be configured to transmit one ormore signals for an in-field diagnostics process. According to at leastone aspect, the device under test may be configured to transmit the oneor more signals for an in-field diagnostics process. One or more devices19400 may, in some aspects, be configured to transmit the one or moresignals for an in-field diagnostics process. In at least one aspect, thedevice under test and the one or more devices 19400 may be configured tocollectively transmit the one or more signals for an in-fielddiagnostics process.

As previously noted, the one or more signals for an in-field diagnosticsprocess may, in some aspects, be transmitted by the device under test.According to at least one aspect, a transceiver of the device under testmay be configured to transmit one or more signals for an in-fielddiagnostics process. In some aspects, the device under test may beconfigured to transmit the one or more reference signals to the one ormore devices 19400. In at least one aspect, the device under test may beconfigured to transmit the one or more reference signals to networkaccess node 110 and/or radio communication network 100.

In some aspects, one or more signals may be received for an in-fielddiagnostics process. According to at least one aspect, the device undertest may be configured to receive the one or more signals for anin-field diagnostics process. One or more devices 19400 may, in someaspects, be configured to receive the one or more signals for anin-field diagnostics process. In at least one aspect, the device undertest and the one or more devices 19400 may be configured to collectivelyreceive the one or more signals for an in-field diagnostics process.

In some aspects, the one or more signals for an in-field diagnosticsprocess may be transmitted by one or more devices 19400. According to atleast one aspect, a receiver of the device under test may be configuredto receive one or more signals for an in-field diagnostics process. Thedevice under test may, in some aspects, be configured to receive the oneor more references signals from the one or more devices 19400. In atleast one aspect, the device under test may be configured to receive theone or more reference signals from network access node 110 and/orterminal device 104. While the one or more signals have been describedin the context of an in-field diagnostics process, above-describedsignaling for an in-field diagnostic process may also be applicable tosome aspects of an in-field calibration process.

The device under test may, in some aspects, be configured to perform atleast a portion of one or more measurements of the one or more signals.In at least one aspect, the device under test may be configured toperform at least a portion of one or more measurements of the one ormore reference signals. The device under test may, in some aspects, beconfigured to report the one or more measurements for analysis. In atleast one aspect, the device under test may be configured to report theone or more measurements to the one or more devices 19400.

The one or more devices 19400 may, in some aspects, be configured toperform at least a portion of one or more measurements of the one ormore signals. In at least one aspect, the one or more devices 19400 maybe configured to perform at least a portion of one or more measurementsof the one or more reference signals. The one or more devices 19400 may,in some aspects, be configured to report the one or more measurementsfor analysis.

With continued reference to FIG. 195 , in some aspects, a result of thein-field diagnostic process may be analyzed 19506 after the in-fielddiagnostic process is completed. In some aspects, one or measurementsmay be compared to one or more performance metrics. According to atleast one aspect, the device under test may be configured to compare theone or more measurements with the one or more performance metrics. Oneor more devices 19400 may, in some aspects, be configured to compare theone or more measurements with the one or more performance metrics. In atleast one aspect, the device under test and the one or more devices19400 may be configured to collectively compare the one or moremeasurements with the one or more performance metrics.

With continued reference to FIG. 195 , in some aspects, it is determinedas to whether one or more countermeasures are to be performed 19508 uponanalyzing one or more result of the in-field diagnostic process 19506.In some aspects, the device under test may be configured to determinewhether one or more countermeasures are to be performed based on the oneor more measurements. According to at least one aspect, the one or moredevices 19400 may, in some aspects, be configured to determine whetherone or more countermeasures are to be performed based on the one or moremeasurements. The device under test and the one or more devices 19400may, in some aspects, be configured to collectively determine whetherone or more countermeasures are to be performed based on the one or moremeasurements. In at least one aspect, one or more countermeasures may beperformed when the one or more measurements fails to meet one or moreprescribed criteria (e.g., predetermined threshold).

In some aspects, the device under test may be configured to determinewhether one or more countermeasures are to be performed based on acomparison between the one or more measurements with the one or moreperformance metrics. According to at least one aspect, the one or moredevices 19400 may, in some aspects, be configured to determine whetherone or more countermeasures are to be performed based on a comparisonbetween the one or more measurements with the one or more performancemetrics. The device under test and the one or more devices 19400 may, insome aspects, be configured to collectively determine whether one ormore countermeasures are to be performed based on a comparison betweenthe one or more measurements with the one or more performance metrics.In at least one aspect, one or more countermeasures may be performedwhen the one or more measurements fails to meet one or more performancemetrics (e.g., predetermined performance metric ranges).

With continued reference to FIG. 195 , in some aspects, one or morecountermeasures for the device under test may be performed 19510 upon adetermination thereof. In some aspects, the device under test may beconfigured to perform at least a portion of one or more countermeasuresfor the device under test. According to at least one aspect, the one ormore devices 19400 may, in some aspects, be configured to perform atleast a portion of one or more countermeasures for the device undertest. The device under test and the one or more devices 19400 may, insome aspects, be configured to collectively perform at least a portionof one or more countermeasures for the device under test.

Various countermeasures may, in some aspects, be performed for thedevice under test. According to at least one aspect, the one or morecountermeasures may include the adjustment of one or more parametersand/or characteristics for one or more components of the device undertest. For instance, one or more coefficients may, in some aspects, beupdated for one or more components for the device under test. In atleast one aspect, the one or more coefficients may include “performance”or “aging” coefficients (e.g., offsets) to counter age or environmentaldegradation.

In some aspects, the one or more countermeasures may include thecorrection of a frequency, time, and/or protocol, for example. The oneor more countermeasures may, for instance, include adding a frequencyoffset to a reference clock, removing a frequency offset to a referenceclock, adding a power gain for transmission, removing a power gain fortransmission, adding a power gain for reception, removing a power gainfor reception, changing a support band, changing a frequency, changing amodulation scheme, and/or changing a multiple input multiple output(MIMO) configuration, for example. In at least one aspect, the frequencyoffset may be an additional frequency offset or a portion of a frequencyoffset. According to some aspects, the reference clock may be a crystaloscillator. The changing of a support band, a frequency, a modulationscheme, and/or a MIMO configuration may be performed by the device undertest to disable one or more configurations therein, which fail to meetone or more prescribed conditions.

Additionally or alternatively, one or more countermeasures may includethe changing of a preference (e.g., priority) for one or more of theradio communication technologies described herein. In some aspects, thedevice under test and/or the one or more devices 19300 may be configuredto change the preference for one or more radio communicationtechnologies when one or more performance metrics are not satisfied.According to at least one aspect, a default preference list for one ormore radio communication technologies (e.g., LTE>3G>GSM) may be adaptedto an alternative preference list for one or more radio communicationtechnologies (e.g., GSM>3G>LTE) when one or more performance metrics(e.g., predetermined threshold, predetermined ranges, among others)associated with the default priority of radio communication technologyare not satisfied. Although a particular number of radio communicationtechnologies and specific methodology for indicating a preferencethereof are described, more or fewer radio communication technologiesmay be included, different radio communication technologies may beimplemented and/or different methodologies for indicating a preferencefor one or more radio communication technologies may be employed. Thedevice under test may, in some aspects, be equipped with one or moreredundant components. According to at least one aspect, the one or morecountermeasures may include identifying one or more components of thevehicular communication device or any portion(s) thereof to be replacedfor failing to meet one or more prescribed conditions, notifying one ormore components of the device under test or any portion(s) thereof to bereplaced, disabling one or more components of the device under test orany portion(s) thereof, identifying one or more redundant components ofthe device under test, and/or activating one or more redundantcomponents of the device under test in favor of one or more disabledcomponents of the device under test or any portion(s) thereof, forexample.

In some aspects, the one or more redundant components of the deviceunder test may be separate and distinct (e.g., mutually exclusive) fromthe one or more disabled components of the device under test. Accordingto at least one aspect, the one or more redundant components of thedevice under test may be include one or more components of the one ormore disabled components of the device under test. The number of the oneor more redundant components of the device under test may, in someaspects, be greater than or equal to the one or more disabled componentsof the device under test. In at least one aspect, the number of the oneor more redundant components of the device under test may be less thanor equal to the one or more disabled components of the device undertest.

Various other countermeasures may, in some aspects, be determined basedon the one or more measurements. According to at least one aspect, theone or more countermeasures may include performing an OTA update,reporting an updated capability of the device under test, reporting anupdated performance of the device under test, and/or requesting anantenna change, for example.

Various downloadable features may, in some aspects, be made available tothe device under test through an OTA update. According to at least oneaspect, one or more downloadable features may be made available byvarious entities, including a manufacturer (e.g., vehicularcommunication device manufacturer), the radio communication network 100,the component provider, the device under test and/or the user (e.g.,owner), among others. In some aspects, the downloadable features may beeither be mandatory (e.g., required) or optional (e.g., enhancedperformance).

The one or more downloadable features may, in some aspects, be designedfor the device under test. According to at least one aspect, the deviceunder test may be provisioned with an OTA update based on a radiocommunication technology. In some aspects, the device under test may beconfigured to update at least a portion of one or more radiocommunication technologies supported by the device under test via an OTAupdate. In at least one aspect, the device under test may be configuredto receive at least a portion of one or more radio communicationtechnologies not already supported by the device under test via an OTAupdate.

In the vehicular context, for instance, the one or more downloadablefeatures may, in some aspects, be designed for vehicular communicationdevice 500. According to at least one aspect, vehicular communicationdevice 500 may be provisioned with an OTA update, for example, based ondata received therefrom. In some aspects, vehicular communication device500 may be configured to provision the performance of vehicularcommunication device 500 for different users based on the OTA update. Inat least one aspect, steering and movement system 502 may be provisionedwith an OTA update to optimize various types of performance (e.g.,sport, comfort, among others).

With continued reference to FIG. 195 , one or more countermeasures forthe device under test may be logged upon performance thereof. In someaspects, the device under test may be configured to log at least aportion of the one or more countermeasures in a memory (e.g., memory214). According to some aspects, the one or more devices 19400 may beconfigured to log at least a portion of the one or more countermeasuresin a memory (e.g., a local memory). After logging the one or morecountermeasures of the device under test 19512, the process may returnto the determination as to whether one or more events are detected19502.

FIG. 196 shows an exemplary flow diagram 19600 for a device under test(e.g., terminal device 102, vehicular communication device 500, amongothers) according to some aspects. As shown in FIG. 196 , flow diagram19600 may begin with a determination of one or more initial conditions19602. Upon determining the one or more initial conditions 19602, adetermination as to whether one or more events are detected 19502. If itis determined that one or more events are not detected, the process mayreturn to determining whether one or more events are detected 19502. Ifit is determined that one or more events are detected, an in-fielddiagnostic process of the device under test may be performed 19504.After the in-field diagnostic process is completed, a result of thein-field diagnostic process may be analyzed 19506. Upon analyzing theresult of the in-field diagnostic process 19506, it is determined as towhether one or more countermeasures are to be performed 19508. If it isdetermined that one or more countermeasures are to be performed, one ormore countermeasures for the device under test may be performed 19510.If it is determined that an error occurs in performing the one or morecountermeasures 19604, then a notification of the error is provided19606. If, however, it is determined that no errors occur in performingthe one or more countermeasures, then a conformance test 19608 may beperformed. Subsequent to performing the one or more countermeasures forthe device under test 19510, one or more countermeasures for the deviceunder test may be logged 19512. After logging the one or morecountermeasures of the device under test 19512, the process may returnto the determination as to whether one or more events are detected19502.

A description of the processes from FIG. 195 is hereby incorporated byreference to FIG. 196 . In some aspects, flow diagram 19600 of FIG. 196may begin with one or more initial conditions being set 19602. Accordingto at least one aspect, the device under test may be configured todetermine one or more initial conditions for in-field diagnosticprocess. The one or more devices 19400 may, in some aspects, beconfigured to determine one or more initial conditions of an in-fielddiagnostic. In at least one aspect, the device under test and the one ormore devices 19400 may be configured to collectively determine one ormore initial conditions of an in-field diagnostic.

Various initial conditions may be set for an in-field diagnosticprocess. In some aspects, one or more initial conditions may include abaseline performance of the device under test (e.g., model specificperformance, generic performance, historical performance, among others),a location of where an-field diagnostic process is to be performed(e.g., home, a location where an in-field diagnostic was previouslycompleted for the device under test, among others), and/or a timinginformation for performing an in-field diagnostic process (e.g., timesince the last in-field-diagnostic process), among others.

With continued reference to FIG. 196 , a determination may be made as towhether an error occurred 19604 in connection with the performance ofone or more countermeasures 19510. In some aspects, the device undertest may be configured to determine whether an error occurred during theperformance of one or more countermeasures. According to at least oneaspect, the one or more devices 19400 may be configured to determinewhether an error occurred during the performance of one or morecountermeasures. The device under test and the one or more devices 19400may, in some aspects, be configured to collectively determine whether anerror occurred during the performance of one or more countermeasures.

Various types of errors may occur during the performance of one or morecountermeasures. In some aspects, an error may include a hardware error,a software error, a hardware/software error, a missing function, a wrongfunction, corrupted data file(s), error recovery from hardware, outdatedconstant(s), incorrect variable(s), and/or version identificationerrors, among others.

With continued reference to FIG. 196 , a notification of error isprovided 19606 based on its detection. In some aspects, the device undertest may be configured to provide a notification of a detected error.According to at least one aspect, the one or more devices 19400 may beconfigured to provide a notification of a detected error. The deviceunder test and the one or more devices 19400 may, in some aspects, beconfigured to collectively provide a notification of a detected error.In at least one aspect, notification of a detected error may be providedto various entities including one or more components (e.g., GUI) of thedevice under test, one or more devices 19400, among others.

With continued reference to FIG. 196 , a notification of error isprovided 19606 in response to detection. In some aspects, the deviceunder test may be configured to provide a notification of a detectederror. According to at least one aspect, the one or more devices 19400may be configured to provide a notification of a detected error. Thedevice under test and the one or more devices 19400 may, in someaspects, be configured to collectively provide a notification of adetected error. In at least one aspect, notification of a detected errormay be provided to various entities including one or more components ofthe device under test (e.g., GUI), one or more devices 19400, amongothers.

With continued reference to FIG. 196 , a conformance test 19608 of thedevice under test may, in some aspects, be performed when it isdetermined that no errors and/or non-critical errors were detected inperforming the one or more countermeasures. In some aspects, conformancetesting may include the in-field diagnostic process of the device undertest 19504 or any portion(s) thereof. According to some aspects,conformance testing may focus on the one or more components of thedevice under test to which one or more countermeasures were applied.Thus, a conformance test may, in some aspects, provide a confirmationthat the one or more countermeasures addressed one or more issuesdetected thorough the in-field diagnostic process.

FIG. 197 shows a process 19700 for performing a conformance test of adevice under test (e.g., terminal device 102, vehicular communicationdevice 500, among others) according to some aspects. As shown in FIG.197 , process 19700 may begin with a determination that one or morecomponents of the device under test are to be augmented 19702. In someaspects, augmentation may include any of the countermeasures describedherein, for example those described with respect to FIG. 195 . Upondetermining that one or more components of a device under test is to beaugmented, one or more components may be notified 19704. According to atleast one aspect, the one or more components to be augmented may bedisabled in response to receiving such a notification. After the one ormore components of the device under test are augmented, a conformancetest of the one or more components may be performed 19706. As notedabove, conformance testing of the one or more component of the deviceunder test may include the in-field diagnostic process described herein,for example those described with respect to FIG. 195 or any portion(s)thereof.

FIG. 198 shows a process 19800 for performing an OTA update process forterminal device 102 and/or vehicular communication device 500 accordingto some aspects. As shown in FIG. 198 , process 19800 may begin with adetermination as to whether one or more OTA updates are available 19802.In some aspects, terminal device 102 and/or vehicular communicationdevice 500 may be configured to request whether or not an OTA update isavailable. According to some aspects, the one or more devices 19400 maybe to determine whether an OTA update is available for terminal device102 and/or vehicular communication device 500 based on an identificationinformation associated therewith. Upon determining its availability, anOTA update for terminal device 102 and/or vehicular communication device500 may be performed 19804 using any of the methods described herein.After performing the OTA update, an action may be performed based on theupdate 19806. For instance, a conformance test may, in some aspects, beperformed for one or more components, which are associated with the OTAupdate. In at least one aspect, one or more signals may be transmittedand/or received by terminal device 102 and/or vehicular communicationdevice 500 in response to the OTA update. According to some aspects,terminal device 102 and/or vehicular communication device 500 may beconfigured to send a confirmation message to a provider of the OTAupdate (e.g., one or more devices 19400).

FIG. 199 is an exemplary message sequence chart 19900 showing theexchange of messages between device under test (e.g., terminal device102, vehicular communication device 500, among others) and the radiocommunication network 100. As shown in FIG. 199 , the device under testmay be configured initiate a test sequence 19902. In some aspects, thismay include providing a message to the radio communication network 100in response to detecting one or more events. According to at least oneaspect, the detection of one or more events may, for instance, beperformed according to one or more aspects described herein, for examplethose described in connection with FIG. 195 . Responsive thereto, theradio communication network 100 may, in some aspects, be configured toprovide one or more reference signals 19904 to the device under testover a downlink communication channel. In response to receiving the oneor more reference signals 19904, the device under test may be configuredto analyze the one or more reference signals and determine if one ormore countermeasures are to be performed 19906. In at least one aspect,the analysis of one or more reference signals and/or determination as towhether one or more countermeasures are to be applied may, for instance,be performed according to one or more aspects described herein, forexample those described in connection with FIG. 195 .

With continued reference to FIG. 199 , the device under test may beconfigured to send one or more reference signals 19908 to the radiocommunication network 100 in response to this analysis and determination19906. Upon receipt, the radio communication network 100 may beconfigured to perform an analysis of the one or more reference signalsfrom the device under test 19910. An analysis result may be reported19912 by the radio communication network 100 upon such a determination.The device under test may be configured to evaluate the analysis resultfrom the radio communication network 100 and determine if one or morecountermeasures should be applied 19914. As previously noted, theanalysis of one or more reference signals and/or determination as towhether one or more countermeasures are to be applied may, for instance,be performed according to one or more aspects described herein, forexample those described in connection with FIG. 195 .

FIG. 200 shows an exemplary method 20000 for communicating over a radiocommunication network in accordance with some aspects. In method 20000for communicating over a radio communication network, the methodincludes identifying one or more components to be modified 20002,applying one or more countermeasures based on the identification of theone or more components to be modified 20004, and communicating based onthe performed one or more countermeasures 20006.

FIG. 201 shows an exemplary method 20100 for communicating over a radiocommunication network in accordance with some aspects. In method 20100for communicating over a radio communication network, the methodincludes applying one or more countermeasures based on an identificationof one or more components to be modified 20102, and communicating basedon the performed one or more countermeasures 20104.

In-Field Diagnostics and Calibration

Vehicular communication devices have emerged into the market with dataconnection rates provided by next-generation broadband networks.Equipped with next-generation data connection rates, vehicularcommunication devices may be configured to access road infrastructuredata to promote safety, energy efficiency and/or enhanced userexperience, among others. In addition to supporting next-generation dataconnection rates, one or more components of a vehicular communicationdevice (e.g., cellular modem) may facilitate the introduction ofadvanced telematics and connected infotainment features. Thus,smartphone connectivity may be provided to users for a wide array ofconnected devices, including their car.

Unlike conventional components designed for smartphones, the lifecycleof the components in a vehicular communication device may be designed toexceed that of some consumer electronics. This difference suggests theeffect of aging on components within a vehicular communication devicemerits consideration. For example, the degradation of modem transistorsover time may lead to decreased switching speeds, or even to componentfailures. Further, as transistors are scaled to smaller geometries,speed and transistor density increase, whereas active power pertransition may decrease. Coupled with the aging effect, however, theprobability that a component could exhibit adverse performance or evenexperience a catastrophic failure increases with scaling.

Another technical problem lies in hardware complexity. A component, suchas a cellular modem, in a vehicular communication device may target ahigher data rate and shorter latency that that of legacy modems (e.g.,FM, DVB, DAB, WiFi). In view of this added complexity, one or morecomponents of a vehicular communication may susceptible to the effectsof aging.

FIG. 193 shows an exemplary internal configuration of radiocommunication arrangement 504 and antenna system 506 of a vehicularcommunication device 500 according to some aspects. As shown in FIG. 193, radio communication arrangement 504 may include a baseband integratedcircuit 19302, a baseband RF integrated interface circuit 19304, RFintegrated circuit 19306, RF integrated circuit 19308, envelope tracking(ET) integrated circuit 19310, ET integrated circuit 19312, LNA bank19314, LNA bank 19316, PA integrated circuit 19318, PA integratedcircuit 19320, duplexer 19322, and duplexer 19324. Although a basebandintegrated circuit 19302, a baseband RF integrated interface circuit19304, RF integrated circuit 19306, RF integrated circuit 19308, ETintegrated circuit 19310, ET integrated circuit 19312, LNA bank 19314,LNA bank 19316, PA integrated circuit 19318, PA integrated circuit19320, duplexer 19322, and duplexer 19324 are illustrated in radiocommunication arrangement 504, some aspects may employ additional orfewer baseband integrated circuits, baseband RF integrated circuits, RFintegrated circuits, ET integrated circuits, LNA banks, PA integratedcircuits, duplexers and/or other elements.

With continued reference to FIG. 193 , RF integrated circuit 19306 may,in some aspects, be configured for a first set of frequency bands,whereas RF integrated circuit 19308 may be configured for a second setof frequency bands. According to at least one aspect, the first set offrequency bands may be the same set of frequency bands as the second setof frequency bands. The first set of frequency bands may, in someaspects, be mutually exclusive from the second set of frequency bands.In at least one aspect, the first set of frequency bands may overlap, atleast in part, in frequency with the second set of frequency bands.

With continued reference to FIG. 193 , antenna system 506 may includeantenna tuner 19326. Although antenna tuner 19326 is illustrated inantenna system 506, some aspects may employ additional or fewer antennatuners and/or other elements. As previously described with respect toFIG. 6 , antenna system 506 may also include a single antenna, anantenna array that includes multiple antennas, an analog antennacombination and/or beamforming circuitry.

While certain aspects are described herein in the context of a vehicularcommunication device 500, it should be noted that a terminal device 102and a terminal device implemented 102 as a vehicular communicationdevice 500 may face similar challenges due to overlapping designconstraints. For instance, one or more components of a vehicularcommunication device 500 may, in some aspects, be configured inaccordance with one or more communication protocols of radiocommunication network 100. According to at least one aspect, the numberof external RF font end components in a cellular modem of a vehicularcommunication device 500 may increase with respect to the number offrequency bands supported by the radio communication network 100. Inthis regard, a TX feedback receiver may, in some aspects, be addedwithin the cellular modem to communicate in accordance with one or morecommunication protocols of the radio communication network 100. In atleast one aspect, the additional TX feedback receiver may be configuredto perform closed loop power control to achieve a power ramping timewithin 1 ms (70 μs for LTS sounding reference signals (SRS)). While thepreceding example is merely illustrative in nature, the added hardwarecomplexity may contribute to the effect of aging on one or morecomponents of a vehicular communication device 500. Accordingly,conventional diagnostics performed on vehicular communication device 500or even terminal device 102 insufficient in detecting the effect(s) ofaging because such diagnostics occur prior to mass deployment.

In view of the foregoing, in some aspects, providing a framework forin-field diagnostics and in-field calibration may be beneficial. In someaspects, an in-field diagnostic process may detect one or more issues(e.g., hardware, software, hardware and/or software, among others)within a terminal device 102. A detected issue may, for instance, beattributable to one or more components of a terminal device 102, such asa failing RF front-end component, a drift in the clock of a localfrequency oscillator, among others. According to at least one aspect, anin-field calibration process may be performed to compensate for an issuedetected through the in-field diagnostic process. An in-fieldcalibration process may, in some aspects, address one or more issuesthat are detected through an in-field diagnostic process. As a result,the added burden of, for instance, uninstalling a component and sendingit back to the factory can be avoided.

Terminal device 102 may be configured to interface with one or moredevices for in-field diagnostics and/or in-field calibration. FIG. 194shows an exemplary configuration in accordance with some aspects whereterminal device 102 interface with one or more devices 19400. As shownin FIG. 194 , for instance, terminal device 102 may be configured tocommunicate with network access node 110, terminal device 104, and/oritself. Although terminal device 102 may interface with network accessnode 110, terminal device 104, and/or itself as shown in FIG. 194 , someaspects may employ additional or fewer interfaces with network accessnodes, terminal devices, and/or other devices.

In some aspects, the one or more devices 19400 may include a terminaldevice, a vehicular communication device, a network access node, acore-network entity, an authentication entity, an Internet of Things (I)device, a road side unit (RSU), a drone, an IoT fuel pump, anelectric-vehicle charging station, automotive service/repair stationequipment, and/or network service provider equipment, among others.According to at least one aspect, the one or more devices 19400 may beincluded in the radio communication network 100. Additionally oralternatively, the one or more devices 19400 may be included on anexternal data network. As further described herein, the one or moredevices 19400 may, in some aspects, be “certified” to facilitatein-field diagnostics and/or in-field compensatory measures.

Terminal device 102 and the one or more devices 19400 may, in someaspects, be configured to communicate via one or more of the radiocommunication technologies described herein. According to at least oneaspect, terminal device 102 may be configured to communicate withnetwork access node 110 through interface 19402. Interface 19402 may,for instance, include an uplink communication channel and/or a downlinkcommunication channel. In some aspects, terminal device 102 may beconfigured to communicate with terminal device 104 through interface19404. Interface 19404 may, for example, include a peer-to-peercommunication link, such as 3GPP sidelink based D2D, V2V communications,Bluetooth, BTLE, WiFi Direct, among others.

Terminal device 102 may, in some aspects, be configured to communicatewith itself via interface 19406. Interface 19406 may, for instance,include an internal TX-RX feedback path, an external feedback loop,among others. According to at least one aspect, the transmitter andreceiver of terminal device 102 may be configured to operate (e.g.,concurrently) on the same carrier frequency. By operating on the samefrequency, the transmitted signals may, in some aspects, be routed intothe receiver within the same hardware platform of terminal device 102.

In some aspects, an in-field diagnostic and/or an in-field calibrationmay be implemented by executing one or more run-time processes.According to at least one aspect, terminal device 102 may be configuredto execute at least a portion of an in-field diagnostic process and/oran in-field calibration process of terminal device 102. For instance,terminal device 102 may, in some aspects, be configured to execute atleast a portion of in-field diagnostic process and/or an in-fieldcalibration process in an unsupervised mode of operation. In at leastone aspect, the one or more devices 19400 may be configured tofacilitate at least a portion of the in-field diagnostic process and/oran in-field calibration process of terminal device 102. According tosome aspects, the one or more devices 19400 may, for instance, beconfigured to execute at least a portion of the in-field diagnosticprocess and/or an in-field calibration process of terminal device 102 ina supervised mode of operation.

An unsupervised mode of operation may, in some aspects, be performedwithout the assistance of the one or more devices 19400. According to atleast one aspect, however, the unsupervised mode of operation mayinclude some form of communication with the one or more devices 19400.In some aspects, the terminal device 102 may be configured exchange oneor more messages with the radio communication network 100 in theunsupervised mode of operation concurrently with the in-field diagnosticprocess and/or an in-field calibration process of terminal device 102.In at least one aspect, the one or more messages may include anintra-frequency measurement report to a network access node 110 duringan idle state connection therewith.

In some aspects, the supervised mode of operation may, for instance, beperformed with the assistance of the one or more devices 19400.According to at least one aspect, the one or more devices 19400 may beconfigured to control at least a portion of the in-field diagnosticprocess and/or an in-field calibration process of terminal device 102 inthe supervised mode of operation. The one or more devices 19400 may, insome aspects, be configured to issue one or more instructions toterminal device 102 in the supervised mode of operation concurrentlywith the in-field diagnostic process and/or an in-field calibrationprocess of terminal device 102.

An in-field diagnostic process and/or an in-field calibration process ofterminal device 102 may, in some aspects, be a software-defined radio(SDR) component implemented by one or more processors configured toexecute software-defined instructions. Although certain aspects hereinmay describe the in-field diagnostic process and/or an in-fieldcalibration process from the perspective of a terminal device 102, thein-field diagnostic process and/or an in-field calibration process, orany portion(s) thereof, may be executed in the terminal device 102 andthe one or more devices 19400, individually or collectively. In someaspects, one or more processors of terminal device 102 (e.g., digitalsignal processor 208, controller 210, application processor 212, amongothers) and/or the one or more devices 19400 (e.g., radio transceiver304, physical layer processor 308, protocol controller 310, amongothers) may be configured to execute at least a portion of the in-fielddiagnostic process and/or an in-field calibration process of terminaldevice 102.

FIG. 202 shows an exemplary in-field diagnostic process 20200 of adevice under test (e.g., terminal device 102) according to some aspects.As shown in FIG. 202 , in-field diagnostic process 20200 may include thedetection of one or more events 20202 associated with the device undertest. Upon detecting one or more events 20202 associated with the deviceunder test, the in-field diagnostic process 20200 may further includethe execution of one or more test signals 20204. After executing one ormore test signals 20204, the in-field diagnostic process 20200 mayfurther include an evaluation of the result(s) of the one or more testsignals 20206. In response to evaluating the result(s) of the one ormore test signals 20206, the in-field diagnostic process 20200 mayfurther include an update to the status of one or more components 20208of the device under test. Upon updating the status of the one or morecomponents 20208 of the device under test, the in-field diagnosticprocess 20200 may further include a determination of whether one or morein-field diagnostic process criteria is satisfied 20210. If it isdetermined that the in-field diagnostic process criteria is satisfied20210, the in-field diagnostic process 20200 may be completed 20212. If,however, it is determined that the in-field diagnostic process criteriais not satisfied 20210, the in-field diagnostic process 20200 mayfurther include the selection of one or more additional test signals forexecution 20212. Upon selecting one or more additional test signals forexecution 20212, the in-field diagnostic process criteria 20200 maytransition to the execution of one or more test signals 20204.

In some aspects, the detection of one or more events 20202 may be basedone or more conditions, factors, triggers and/or events describedherein. According to at least one aspect, the detection of one or moreevents 20202 may be based on a timing (e.g., countdown timer, timestamp, among others) since a last diagnostic and/or calibration wasperformed. The detection of one or more events 20202 may, in someaspects, be based on one or more key performance indicators (e.g., RSSI,PLR, PER, BER, BLER, MoU, among others). For instance, one or more keyperformance indicators may be compared against one or more predeterminedcriteria to determine whether one or more events 20202 has occurred, isoccurring, and/or is likely to occur in the future. In at least oneaspect, the detection of one or more events 20202 may be determinedbased on a user's input. By way of illustrative example, terminal device102 may be configured to detect an event has occurred in response to auser's input to initiate a diagnostic process of terminal device 102.According to some aspects, the detection of one or more events 20202 maybe based on the one or more devices 19400. Terminal device 102 may beconfigured to detect an event has occurred based on information fromterminal device 104 and/or network access node 110. When terminal device102 is implemented as a vehicular communication device 500, the terminaldevice 102 may, in some aspects, be configured to detect an event hasoccurred based on information from a data center of a manufacturer ofthe vehicular communication device 500. According to at least oneaspect, the data center may monitor (e.g., periodically) one or more KPIof the terminal device 102 and trigger one or more events 20202 thereinbased on a comparison against one or more predetermined criteria (e.g.,KPI is greater than or equal to a threshold).

One or more test signals may be executed 20204 as a part of the in-fielddiagnostic 20200 of the device under test. Before execution may occur,the one or more test signals may be obtained from a memory. According toat least one aspect, the memory may be local to terminal device 102(e.g., pre-loaded to memory 214) and/or external to terminal device 102.The memory may, in some aspects, be local to the one or more devices19400 and/or external to the one or more devices 19400. In at least oneaspect, terminal device 102 may be configured to obtain the one or moretest signals by transmitting a request to terminal device 104, networkaccess node 110, one or more internal servers within the radiocommunication network 100, and/or one or more external servers to theradio communication network 100, among others. According to someaspects, the one or more devices 19400 may be configured to obtain theone or more test signals by transmitting a request to terminal device102, one or more internal servers within the radio communication network100, and/or one or more external servers to the radio communicationnetwork 100, among others.

In some aspects, terminal device 102 and/or the one or more devices19400 may be configured to execute the one or more test signals.According to at least one aspect, the execution of one or more testsignals may include processing, transmitting and/or receiving one ormore test signals. The one or more test signals may, in some aspects, beimplemented in accordance with a standardized communication protocol(e.g., 3G, LTE, among others) or a non-standardized approach.

Terminal device 102 and/or the one or more devices 19400 may, forinstance, be configured to define at least one aspect of the one or moretest signals in a standardized and/or non-standardized approach.According to at least one aspect, the one or more test signals mayinclude one or more waveforms (e.g., sine wave, cosine wave, pulse wave,square wave, among others) in which the amplitude, phase, frequency,start and/or stop of the one or more test signals may be varied overtime. In some aspects, terminal device 102 may have more flexibility indefining the one or more test signals in the non-standardized approachwhen the one or more test signals are received through the internalTX-RX feedback path because the one or more signals are not transmittedover the air interface.

After executing one or more test signals 20204, the in-field diagnosticprocess 20200 may further include an evaluation of the result(s) of theone or more test signals 20206. In some aspects, terminal device 102and/or the one or more devices 19400 may be configured to perform atleast a portion of the evaluation of the one or more test signals 20204.According to at least one aspect, terminal device 102 and/or the one ormore devices 19400 may be configured to transmit and/or receive one ormore measurements of the one or more test signals 20206. The terminaldevice 102 and/or the one or more devices 19400 may, in some aspects, beconfigured to compare the one or more measurements (e.g., spur, spectrummask, spectrum flatness, frequency offset, error vector magnitude (EVR),adjacent channel leakage ratio (ACLR) derivation, among others) to oneor more predetermined criteria (e.g., thresholds, waveforms, amongothers).

In some aspects, the one or more test signals may be organized andincluded within one or more test patterns to facilitate the comparisonof their respective results. FIG. 203 shows an exemplary evaluation20300 in accordance with some aspects where various test patterns aredesigned to test the performance of one or more components of terminaldevice 102. As shown in FIG. 203 , evaluation 20300 includes anevaluation of test pattern 20302, test pattern 20304, test pattern20306, and test pattern 20308. Although test pattern 20302, test pattern20304, test pattern 20306, and test pattern 20308 are illustrated inFIG. 203 , some aspects may employ additional or fewer test patterns.

Each test pattern may be configured to test the performance of one ormore components of terminal device 102. In FIG. 203 , test pattern 20302is illustrated as being configured to test the performance of LNA 19314and PA 19318, whereas test pattern 20304 is depicted as being configuredto test the performance of LNA 19314 and PA 19320. By way of contrast,test pattern 20306 is shown in FIG. 203 to test the performance of LNA19316 and PA 19318, whereas test pattern 20308 is graphicallyrepresentative of testing the performance of LNA 19316 and PA 19320.While each of the test patterns illustrated in FIG. 203 is configured totest two components of the terminal device 102, some aspects may employadditional or fewer components of terminal device 102 being tested byeach test pattern.

A result of evaluating the one or more test signals may take variousforms. In some aspects, the one or more test signals may result in ahard decision (e.g., pass decision or fail decision), or a soft decision(e.g., probabilistic expression) for one or more components of terminaldevice 102. According to at least one aspect, a hard decision mayrepresent a binary decision and/or have a degree of certainty associatedtherewith. A pass decision may, in some aspects, represent a decisionbetween a pass decision and a fail decision. In one illustrativeexample, a hard decision may be associated with a first degree ofcertainty (e.g., 75%) that one or more components of terminal device 102passed a particular test. In at least one aspect, a soft decision may beassociated with a second degree of certainty (e.g., 50%) that one ormore components of terminal device 102 passed a particular test.According to some aspects, a fail decision may be associated with athird degree of certainty (e.g., 25%) that one or more components ofterminal device 102 has passed a particular test. Although certainaspects herein describe three types of decisions resulting from the oneor more test signals, some aspects may employ additional or fewer typesof decisions.

In some aspects, each of the degrees of certainty may represent or beexpressed as a value (e.g., numerical percentage), a plurality ofvalues, a range of values, a plurality of ranges of values, and/ormathematical equation, for example. When expressed as a value, forinstance, the first degree of certainty may be greater than or equal tothe second degree of certainty, whereas the second degree of certaintymay be greater than or equal to the third degree of certainty. Accordingto at least one aspect, one or more results may be combined (e.g.,added, subtracted, multiplied, filtered by a step function, amongothers) in order to narrow down which component(s) of terminal device102 is at fault. In at least one aspect, terminal device 102 and/or theone or more devices 19400 may be configured to evaluate the result(s) ofthe one or more test signals 20206 based on data associated with asingle result or a combined set of results (e.g., using a look-uptable). In this fashion, a single result or a plurality of results maybe used to inform a decision about a component of terminal device 102.

With continued reference to FIG. 203 , the unshaded portions surroundingtest pattern 20302 and test pattern 20304 are illustrative of a passdecision. In contrast, the shaded portions surrounding test pattern20306 and pattern 20308 are illustrative of a fail decision. As shown inFIG. 203 , LNA 19314 is illustrated as receiving a pass decision fortest pattern 20304 and test pattern 20306. PA 19318 is depicted asreceiving a pass decision for test pattern 20302 and a fail decision fortest pattern 20306. PA 19320 is shown to receive a pass decision fortest pattern 20304 and a fail decision for test pattern 20308. LNA 19316is graphically represented as receiving a fail decision for test pattern20306 and a fail decision for test pattern 20308. Based on these testpatterns, terminal device 102 and/or the one or more devices 19400 maybe configured to determine that LNA 19316 is the most likely to be afault.

In response to evaluating the result(s) of the one or more test signals20206, the in-field diagnostic process 20200 may further include anupdate to the status of one or more components 20208. With continuedreference to FIG. 203 , terminal device 102 and/or the one or moredevices 19400 may, in some aspects, be configured to update the statusof one or more components of terminal device 102. According to at leastone aspect, the status of LNA 19316 may be updated with a fail decision(e.g., fault), whereas LNA 19314, PA 19318 and/or PA 19320 may updatedwith a pass decision. Additionally or alternatively, the status of eachof these components may be updated with a respective degree of certaintyof passing one or more these test patterns.

Upon updating the status of the one or more components 20208 of thedevice under test, the in-field diagnostic process 20200 may furtherinclude a determination of whether one or more in-field diagnosticprocess criteria is satisfied 20210. In some aspects, the in-fielddiagnostic process criteria may include determining whether a predefinednumber of the one or more components of the device under test have beenevaluated. In this regard, terminal device 102 and/or the one or moredevices 19400 may be configured to determine whether a degree ofcertainty associated with one or more components of terminal device 102satisfies a predetermined condition (e.g., threshold).

In some aspects, the in-field diagnostic process criteria may includedetermining whether a predetermined number of iterations of thediagnostic process has been reached. According to at least one aspect,terminal device 102 may be configured to receive a user's inputindicative of the predetermined number of iterations of the diagnosticprocess. Additionally or alternatively, this information may bedetermined based on a remaining battery power level of the device undertest, a remaining battery power level of the one or more devices 19400,a manufacture of the device under test, a network operator, and/or anentity on an external data network.

If it is determined that the in-field diagnostic process criteria issatisfied 20210, the in-field diagnostic process 20200 may be completed20212. In some aspects, terminal device 102 may be designated as“certified” if one or more test patterns are passed. According to atleast one aspect, the terminal device 102 may be configured tofacilitate the in-field diagnostic process of an “uncertified” terminaldevice. This certification process may be implemented by one or moreaspects described herein.

If, however, it is determined that the in-field diagnostic processcriteria is not satisfied 20210, the in-field diagnostic process 20200may further include the selection of one or more additional test signalsfor execution 20214. In some aspects, it may be inefficient to executeall available test patterns before subsequently evaluating and/orcombining one or more results thereof. For instance, such aninefficiency could arise when the number of available test patterns isextraordinarily large. According to at least one aspect, a sub-set oftest patterns may instead be first executed and evaluated to reduce thesearch space of component candidates at fault. Based on these results,terminal device 102 and/or the one or more devices 19400 may beconfigured to select one or more additional test signals in order totest the performance one or more components of terminal device 102within the reduced search space. The in-field diagnostic process 20200may be repeated until one or more diagnostic process criteria issatisfied 20210.

As previously mentioned, terminal device 102 and/or one or more devices19400 may be configured to execute at least a portion of an in-fieldcalibration process of terminal device 102. In some aspects, thein-field calibration process of terminal device 102 may be performed inresponse to the completion of the in-field diagnostic process 20200 ofterminal device 102.

FIG. 204 shows an exemplary internal configuration of radiocommunication arrangement 504 and antenna system 506 of implemented asvehicular communication device 500 according to some aspects. As shownin FIG. 204 , radio communication arrangement 504 may include a basebandintegrated circuit 19302, RF integrated circuit 19306, ET integratedcircuit 19310, PA integrated circuit 19318, switch 20402, duplexer19322, and duplexer 19324. Although a baseband integrated circuit 19302,ET integrated circuit 19310, PA integrated circuit 19318, switch 20402,duplexer 19322 are illustrated in radio communication arrangement 504,some aspects may employ additional or fewer baseband integratedcircuits, RF integrated circuits, ET integrated circuits, PA integratedcircuits, switches, duplexers and/or other elements.

In some aspects, the effect of aging on ET integrated circuit 19310 mayresult in one or more delays on the amplitude modulation (AM) path. Thismay, in some aspects, degrade the quality of the transmit (TX) signalupon amplification. In at least one aspect, vehicular communicationdevice 500 may be configured to perform an in-field calibration process20400 to address the effect of aging on ET integrated circuit 19310. Forinstance, vehicular terminal device 500 may be configured to determine anew delay compensation setting for the ET integrated circuit 19310.

As shown in FIG. 204 , in-field calibration process 20400 may beperformed by one or more components of the vehicular communicationdevice 500. In some aspects, the RF integrated circuit 19306 may beconfigured to adjust a delay compensation setting 20404 of the ET 19310.According to at least one aspect, switch 20402 may be configured toroute the TX signal back through the RX path in an internal TX-RXfeedback path 20406. The RF integrated circuit 19306 may, in someaspects, be further configured to receive the TX signal and measure oneor more characteristics (e.g., spur, EVR, ACLR derivation, among others)of the received TX signal 20408. In at least one aspect, the RFintegrated circuit 19306 may be configured to evaluate the one or moremeasured characteristics of the received TX signal, and generate a newdelay compensation setting 20410 of the ET 19310 based on theevaluation. According to some aspects, the in-field diagnosticcalibration process 20400 may be performed iteratively until the one ormore measurements satisfies one or more prescribed criteria (e.g.,predetermined thresholds).

Once the recalibration process of a device is completed (e.g.,successful), the device may, in some aspects, be configured to repeat adiagnostic process (e.g., in-field diagnostic process 20200) as averification step. As previously mentioned, a device (e.g., terminaldevice 102, vehicular communication device 500, among others) may bedesignated as “certified” if one or more test patterns are passed of thein-field diagnostic process. According to at least one aspect, terminaldevice 102 may, for instance, be configured to generate a certificateupon completing an in-field diagnostic and/or an in-field calibration.Additionally or alternatively, terminal device 102 may be configured toreceive a certificate from the one or more devices 19400 (e.g., externalserver) based on an evaluation the results of the in-field diagnosticand/or the in-field calibration. Upon certification, the terminal device102 may be configured to facilitate at least a portion of an in-fielddiagnostic process and/or of an in-field calibration process of an“uncertified” terminal device in a supervised mode of operation.

FIG. 205 shows an exemplary network configuration 20500 in accordancewith some aspects where terminal device 102 and one or more devices19400 are certified. As shown in FIG. 205 , network configuration 20500includes network access node 110, terminal device 102, and terminaldevice 104, and terminal device N. Although a network access node 110,terminal device 102, and terminal device 104, and terminal device N areillustrated in network configuration 20500, some aspects may employadditional or fewer network access nodes, terminal devices and/or otherelements. For instance, one or more devices 19300 may be configured toact as an intermediary to relay (e.g., pass-through), monitor (e.g.,scan for one or more viruses), verify (e.g., perform a redundantoperation or authenticate) and/or modify (e.g., update, correct, or thelike) data exchanged between network access node 110, terminal device102, terminal device 104, and/or terminal device N.

In some aspects, network access node 110 may be configured to perform atleast a portion of an in-field diagnostic and/or in-field calibration ofterminal device 102 in a supervised mode of operation 20502. Accordingto at least one aspect, terminal device 102 may be configured to receivea certificate from the network access node 110 based on completion ofthe in-field diagnostic and/or the in-field calibration. Additionally oralternatively, terminal device 102 may be configured to change itsstatus to “certified” 20504 based on completion of the in-fielddiagnostic and/or the in-field calibration.

Upon certification, terminal device 102 and/or network access node 110may, in some aspects, be configured to perform at least a portion of anin-field diagnostic and/or an in-field calibration of terminal device104 in a supervised mode of operation 20506. According to at least oneaspect, terminal device 104 may be configured to receive a certificatefrom terminal devices 102 and/or network access node 110 based oncompletion of the in-field diagnostic and/or the in-field calibration.Additionally or alternatively, terminal device 104 may be configured tochange its status to “certified” 20508 based on completion of thein-field diagnostic and/or the in-field calibration.

Although network access node 110, terminal device 102, terminal device104, and terminal device N are illustrated in a series configuration,some aspects may employ other configurations. In some aspects, theabove-described certification procedure, or any portion(s) thereof, maybe performed in a sequential and/or parallel manner. According to atleast one aspect, terminal device 102 may be configured to perform anin-field diagnostic, or any portion(s) thereof, of terminal device N,whereas terminal device 104 may be configured to perform an in-fieldcalibration, or any portion(s) thereof, of terminal device N, or viceversa. Some portion(s) of the in-field diagnostic of terminal device Nmay, in some aspects, be separate in time (e.g., mutually exclusive) oroverlap in time (e.g., concurrent processes, or the like) from thein-field calibration of terminal device N. Eventually, terminal device Nmay be configured to change its status to “certified” 20510 based oncompletion of the in-field diagnostic and/or the in-field calibration ofterminal device N. The aforementioned processes may not only offloadsome of the burden on finite resources of the radio communicationnetwork 100, they may, in some aspects, reduce the amount of calibrationequipment provided by a network operator.

The supervised mode of operation may, in some aspects, provide a certaindegree of assurance that a supervisor device (e.g., master) passed anin-field diagnostic and/or in-field calibration (e.g., within apredetermined period). Through this interaction, a device under test(e.g., terminal device 102) may receive a tested baseline for RFparameters to facilitate an in-field diagnostic and/or an in-fieldcalibration in a supervised mode. In at least one aspect, the supervisedmode of operation may further provide a mechanism to more easily detectcertain issues, such as oscillator drift and frequency offset.

In some aspects, the one or more devices 19400 may be verified before asupervised mode of operation may be established. According to at leastone aspect, the one or more devices 19400 may be configured to receive acertificate after an in-field diagnostic process and/or an in-fieldcalibration is performed on the one or more devices 19400. The terminaldevice 102 may be configured to receive a copy of this certificate fromthe one or more devices 19400 to verify the supervised mode of operationmay be established. This certificate may be valid for a predeterminedperiod (e.g., from issuance) and/or valid for a predefined number (e.g.,2) of uses in a supervised mode of operation.

Another technical problem may be the challenge of predicting the typesof faults which may occur during the life time of a device. In at leastone aspect, an in-field diagnostic process and/or an in-fieldcalibration process may be reconfigured such that their respectivealgorithms may be updated through software. (e.g., by an OTA updateprocess described herein) According to some aspects, a software-designedcheck entity (SDCE) may implemented as one or more processors of, forinstance, terminal device 102, which are configured to executesoftware-defined instructions in order to download one or more updatesfrom the radio communication network 100 or from an external datanetwork. The one or more updates may, in some aspects, include an updateto the in-field diagnostic process and/or the in-field calibrationprocess of terminal device 102. Upon execution, the software definedinstructions may further be configured to generate one or more testsignals and analyze the results received therefrom. In this regard, twoimplementations are shown in FIGS. 206 and 207 .

FIG. 206 shows an exemplary internal configuration 20600 of radiocommunication arrangement 504 in accordance with some aspects. As shownin FIG. 206 , blocks A-E may represent one or more components of thetransmission path, whereas blocks F-J represent one or more componentsof the reception path. In some aspects, SDCE 20602 may be configured tocommunicate with one or more of blocks A-E of the transmission path andone or more of blocks F-J of the reception path. According to at leastone aspect, switch 20402 may be configured to route the TX signal to theRX path by way of an internal TX-RX feedback path 20406. SDCE 20602 may,in some aspects, be configured to generate one or more test signals andanalyze the results therefrom for various combinations of the one ormore blocks A-E of the transmission path and the one or more blocks F-Jof the reception path. In at least one aspect, SDCE 20602 may beconfigured to apply one or more updated in-field diagnostic processand/or one or more updated in-field calibration processes to blocks A-F.

FIG. 207 shows an exemplary internal configuration 20700 of radiocommunication arrangement 504 in accordance with some aspects. As shownin FIG. 207 , blocks A-E may represent one or more components of thetransmission path, whereas blocks F-J represent one or more componentsof the reception path. In some aspects, SDCE 20702 may be configured tocommunicate with an input to blocks A-E of the transmission path and anoutput of blocks F-J of the reception path. According to at least oneaspect, switch 20402 may be configured to route the TX signal to the RXpath by way of an internal TX-RX feedback path 20406. Provided thisconfiguration, SDCE 20602 may, in some aspects, be configured togenerate one or more test signals for and analyze the results receivedfrom an input to blocks A-E of the transmission path and an output ofblocks F-J of the reception path. In at least one aspect, SDCE 20602 maybe configured to apply one or more updated in-field diagnostic processand/or one or more updated in-field calibration processes to blocks A-F.

In some aspects, the in-field diagnostic process and/or in-fieldcalibration process may be implemented without a change to one or morecommunication protocols (e.g., 3GPP) of the radio communication network100 when self-diagnostic and/or self-calibration are applied. Accordingto at least one aspect, various actions may be taken by the device undertest to ensure compatibility with the one or more communicationprotocols. The device under test (e.g., terminal device 102) may, insome aspects, be configured to terminate one or more connections withone or more other devices (e.g., one or more devices 19400). In at leastone aspect, certain connections with the one or more devices 19400 maybe maintained in an assistance mode of operation to facilitate at leasta portion of the in-field diagnostic process and/or the in-fieldcalibration process.

Communication protocol (e.g., 3GPP) support may, in some aspects, beimplemented through one or more new modes of operation: (i)RRC_DIAGNOSTICS mode; and (ii) RRC_CALIBRATION mode. According to atleast one aspect, RRC_DIAGNOSTICS mode may be triggered by the radiocommunication network 100 via a single communication link (e.g., directlink), a plurality of communication links (e.g., multi-cast link),and/or a broadcast link to check of the characteristics (e.g., filtershape, out-of-band (00B) radiation, carrier frequency stability, amongothers) of one or more devices of the radio communication network 100.Depending upon the results of in-field diagnostic, a device under testmay, in some aspects, be configured to perform an internalre-calibration or a re-calibration enforced by the radio communicationnetwork 100 through the RRC_CALIBRATION mode. In at least one aspect,divergent characteristics (e.g., as a result of aging effects) may beaddressed through one or more in-field re-calibration processes.

In some aspects, a target device may be in a “FULLY_OPERATIONAL” (oralternatively “CERTIFIED”) mode (or UE category). According to at leastone aspect, the radio communication network 100 may be configured toenforce the status of a device to “CALIBRATION_REQUIRED” (oralternatively “LIMITED_CERTIFICATION” or “UNCERTIFIED”) when therequirement for a re-calibration is detected. This status may, in someaspects, force the device under test to operate with limitedcommunication functionality. In at least one aspect, limit communicationfunctionality may be limited to those which are required to execute thecalibration and to exchange the corresponding data (e.g., transmissionof diagnostics/calibration results and/or reception of triggers forinitiating the calibration) with the radio communication network 100.According to some aspects, voice communication and/or data communicationmay not be permitted when the device under test is operating in the“CALIBRATION_REQUIRED” mode.

FIG. 208 is an exemplary message sequence chart 20800 showing theexchange of messages between terminal device 102 and the radiocommunication network 100. In some aspects, terminal device 102 mayinterface with the radio communication network 100 through networkaccess node 110. As shown in FIG. 208 , one or more components of theradio communication network 100 may be configured to detect one or moreevents 20802. According to at least one aspect, the detection of one ormore events 20802 may, for instance, be performed according to one ormore aspects described in connection with FIG. 202 .

In response to one or more events being detected 20802 by the radiocommunication network 100, the radio communication network 100 may, insome aspects, be configured to instruct the terminal device 102 enterthe RRC_DIAGNOSTIC mode 20804 over a downlink communication channel.According to at least one aspect, this instruction may specify themanner in which terminal device 102 is to report to the radiocommunication network 100. Terminal device 102 may, in some aspects, beconfigured to perform an in-field diagnostic process (e.g., in-fielddiagnostic process 20200) and provide a diagnostic report 20808 to theradio communication network 100 after entering the RRC_DIAGNOSTIC mode20806.

Upon receipt, the radio communication network 100 may, in some aspects,evaluate the received diagnostic report and determine whethercalibration is required. According to at least one aspect, the radiocommunication network 100 may be configured to instruct the terminaldevice 102 to end the RRC_DIAGNOSTIC mode 20812 when no calibration isrequired 20810. In some aspects, the terminal device 102 may beconfigured to end the RRC_DIAGNOSTIC mode 20814 in response to thereceipt of this instruction.

FIG. 209 is an exemplary message sequence chart 20900 showing theexchange of messages between terminal device 102 and the radiocommunication network 100. In some aspects, terminal device 102 mayinterface with the radio communication network 100 through networkaccess node 110. As shown in FIG. 209 , one or more components of theradio communication network 100 may be configured to detect one or moreevents 20802. According to at least one aspect, the detection of one ormore events 20802 may, for instance, be performed according to one ormore aspects described in connection with FIG. 202 .

In response to one or more events being detected 20802 by the radiocommunication network 100, the radio communication network 100 may, insome aspects, be configured to instruct the terminal device 102 enterthe RRC_DIAGNOSTIC mode 20804 over a downlink communication channel.According to at least one aspect, this instruction may specify themanner in which terminal device 102 is to report to the radiocommunication network 100. Terminal device 102 may, in some aspects, beconfigured to perform an in-field diagnostic process and provide adiagnostic report 20808 to the radio communication network 100 afterentering the RRC_DIAGNOSTIC mode 20806.

Upon receipt, the radio communication network 100 may, in some aspects,evaluate the received diagnostic report and determine whethercalibration is required. According to at least one aspect, the radiocommunication network 100 may be configured to instruct the terminaldevice 102 to enter the RRC_CALIBRATION mode 20904 when it is determinedthat calibration is required 20902. According to at least one aspect,terminal device 102 may be configured to enter the RRC_CALIBRATION mode20906 in responsive to the receipt of this instruction. An in-fieldcalibration process of terminal device 102 may be performed (e.g.,in-field calibration process 20400) and an updated diagnostic report20908 may be provided to the radio communication network 100.

Upon receipt, the radio communication network 100 may, in some aspects,evaluate the updated diagnostic report and determine whether furthercalibration is required. According to at least one aspect, the radiocommunication network 100 may be configured to instruct the terminaldevice 102 to enter the RRC_DIAGNOSTIC mode 20912 when furthercalibration is required 20910, thereby returning the process back to20804.

FIG. 210 is an exemplary message sequence chart 21000 showing theexchange of messages between terminal device 102 and the radiocommunication network 100. In some aspects, terminal device 102 mayinterface with the radio communication network 110 through networkaccess node 110. As shown in FIG. 210 , one or more components of theradio communication network 100 may be configured to detect one or moreevents 20802. According to at least one aspect, the detection of one ormore events 20802 may, for instance, be performed according to one ormore aspects described in connection with FIG. 202 .

In response to one or more events being detected 20802 by the radiocommunication network 100, the radio communication network 100 may, insome aspects, be configured to instruct the terminal device 102 enterthe RRC_DIAGNOSTIC mode 20804 over a downlink communication channel.According to at least one aspect, this instruction may specify themanner in which terminal device 102 is to report to the radiocommunication network 100. Terminal device may, in some aspects, beconfigured to perform an in-field diagnostic process and provide adiagnostic report 20808 to the radio communication network 100 afterentering the RRC_DIAGNOSTIC mode 20806.

Upon receipt, the radio communication network 100 may, in some aspects,evaluate the received diagnostic report and determine whethercalibration is required. According to at least one aspect, the radiocommunication network 100 may be configured to instruct the terminaldevice 102 to enter the RRC_CALIBRATION mode 20904 when it is determinedthat calibration is required 20902. According to at least one aspect,terminal device 102 may be configured to enter the RRC_CALIBRATION mode20906 in responsive to the receipt of this instruction. An in-fieldcalibration process (e.g., in-field calibration process 20400) ofterminal device 102 may be performed and an updated diagnostic report20908 may be provided to the radio communication network 100.

Upon receipt, the radio communication network 100 may, in some aspects,evaluate the updated diagnostic report and determine whether furthercalibration is required. According to at least one aspect, the radiocommunication network 100 may be configured to instruct the terminaldevice 102 to end the RRC_CALIBRATION mode 21004 when no furthercalibration is required 21002. In some aspects, the terminal device 102may be configured to end the RRC_CALIBRATION mode 21006 in response tothe receipt of this instruction.

Certain V2X functionalities and systems, in the context of automotivesystems, may be based on the principles of functional safety. Other V2Xfunctionalities and systems, however, are less likely to be inclusive ofsuch principles. In some aspects, functional safety considerations maydepend upon whether a certain function or service may lead to anunacceptable risk of physical injury, or to impairment or damage to thehealth of people either directly, indirectly or not at all. By way of anillustrative comparison, some aspects of automated emergency breakingfeatures may, for instance, fall within the scope of functional safetyguidelines for compliance, whereas one or more entertainment featuresare less likely to fall within the guidelines.

To inform an in-field diagnostic process and/or an in-field calibrationprocess about functional safety, metadata may be associated with one ormore functions, services, components, building blocks, for example, toprovide functional safety information. In some aspects, a firstfunctional safety tag (e.g., red tag) may indicate that one or morefunctional safety principles merits consideration. According to at leastone aspect, the first functional safety tag may indicate that auditingof a feature is required, and/or inclusion of redundancy for thisfeature is required, for example. A second functional safety tag (e.g.green tag) may, in some aspects, indicate that one or more functionalsafety principles do not merits consideration. As an alternative toproviding the second functional safety tag, the absence of anyfunctional safety tag may implicitly indicate that one or morefunctional safety principles do not apply.

Compliance with one or more functional safety requirements may presentthe added technical challenge of determining which in-field diagnosticprocesses and/or the in-field calibration processes could result in amalfunction or similar may lead to “unacceptable risk” or the like. Insome aspects, further granularity may be added to differentiate one ormore functions, services, components, building blocks, among others.

In some aspects, the first functional safety tag (e.g., red tag) mayfurther indicate that no modification is allowed. By way of illustrativeexample, a result of the in-field diagnostic process and/or the in-fieldcalibration process may include a selection from among pre-defined andpre-tested configurations (e.g. filtered configurations). Additionallyor alternatively, one or more redundancy components may be added to aterminal device to ensure that if one or more components of the terminaldevice is not working as intended, then a selection may be made amongthe one or more redundancy components. Through this process, theterminal device may operate within one or more performance metrics.

The first functional safety tag (e.g., red tag) may, in some aspects,further indicate that modification(s) are permitted within one or morestrictly-defined boundaries. According to at least one aspect, thesetypes of boundaries may be covered or defined by the functional safetyframework and its compliance statements. In some aspects, modificationsmay be limited to specific reconfiguration steps in specific components.By way of illustrative example, a filter in the RF front-end may beconfigured to adapt out-of-band (00B) emission masks or the like.Accordingly, the in-field diagnostic and/or in-field calibrationfeatures may be applied within the one or more pre-defined boundaries.In at least one aspect, a single redundancy component may left availablein a terminal device to ensure that if one or more specific componentsof a terminal device are not working as intended, at least oneredundancy component is available. Through this interaction, at leastone redundancy component should be available if the in-field calibrationprocess fails to address one or more issues detected through thein-field diagnostic process.

When a second functional safety tag (e.g. green tag) is present, and/orin the absence of a functional safety tag, the terminal device may beconfigured to select any remedy to address one or more issues detectedthrough the in-field diagnostic process.

FIG. 211 shows an exemplary method 21100 for communicating over a radiocommunication network in accordance with some aspects. In method 21100for communicating over a radio communication network, the methodincludes performing at least a portion of a calibration process based onan identification of one or more components to be modified 21102, andcommunicating based on a result of the calibration process 21104.

FIG. 212 shows an exemplary method 21200 for communicating over a radiocommunication network in accordance with some aspects. In method 21200for communicating over a radio communication network, the methodincludes identifying one or more components to be modified 21202,performing at least a portion of a calibration process based on theidentification of the one or more components to be modified 21204, andcommunicating based on a result of the calibration process 21206.

Power Resource Optimization for Airborne Application Delivery Systems

Unmanned aerial vehicles (UAV) present opportunities for airborneapplications of various technologies. An airborne vehicle, however,often has a limited power source, and power that otherwise would havebeen used for aviation purposes may be redirected to other applicationson board the UAV. Therefore, there can be a trade-off between providingpower to aviation systems and application systems on a UAV. Optimizationof the power resource may allow the quality of service of an applicationsystem on a UAV to be improved while maintaining flight capabilities ofthe UAV.

As used herein an “unmanned aerial vehicle” or “UAV” may be an airbornevehicle that does not have a pilot in the UAV. The UAV may beautonomously piloted and/or remotely piloted. The UAV may also beassisted piloted aviation, semi-autonomously piloted or autonomouslypiloted except when interrupted by a human/machine, among others. TheUAV may be a fixed wing vehicle or a rotating wing vehicle, or acombination thereof. The UAV may be propelled by a thrust system, e.g.,using rotors, propellers, jet engines, rockets, or any combinationthereof. The UAV may be powered by a fuel system or may be electricallypowered with a battery system.

As used herein, an “aviation system” may include any system thatcontrols flight of the UAV. The aviation system may be understood asincluding components and/or systems that are responsible for theaeronautical and navigational aspects of the UAV. For example, theaviation system may control navigation, flight measurement systems(e.g., airspeed, altitude, pitch-bank, weather, compass, among others),flight control surfaces and/or rotating flight controls, propulsionand/or lift systems, take-off and/or landing systems, among others.

As used herein, an “application system” may be a secondary system on theUAV that provides an additional application for the UAV excluding theaviation system. The application system may interact with objects ortargets external to the UAV. For example, the application may include atelecommunications system that communicates with one or more networkaccess nodes and/or one or more terminal devices; a sensing system,e.g., a video sensing system that uses optical technologies to identifyand/or track objects, or sensing with local sensors (e.g., audio, video,image, position, radar, light, environmental, or any other type ofsensing component) to obtain sensing data; among others.

FIG. 213 shows a UAV 21301. UAV 21301 may include an application system21310, an aviation system 21320, a processor 21330, and a power source21340. Processor 21330 may control interactions between systems on UAV21301, e.g., arbitrate power resources between application system 21310and aviation system 21320, control information flow between applicationsystem 21310 and aviation system 21320, control UAV-wide actions, etc.Power source 21340 may provide power to the systems of the UAV. Powersource 21340 may include a battery. The battery may be charged by anonboard fuel source, e.g., an auxiliary power unit, and/or the batterymay be charged by an onboard passive charging system. In addition, thebattery may be charged by an external power source, e.g., the batterymay be charged from a terrestrial charging station and/or may be chargedmid-flight by another vehicle.

UAV 21301 may include flight control surfaces 21322. The flight controlsurfaces 21322 may be controlled by the aviation system 21320. Flightcontrol surfaces 21322 may include structures for flight and flightcontrol. For example, flight control surfaces 21322 may include one ormore fixed wings, one or more rotatable wings (which may be powered,e.g., a helicopter, or unpowered, e.g., an auto-gyro), one or morerudders, one or more flaps, one or more elevators, one or more ailerons,one or more trim tabs, one or more canards, one or more propulsionsystems (e.g., one or more propellers, one or more rotors, one or morejet engines, etc.), among others.

FIG. 214 shows UAV 21401A and UAV 21401B. UAV 21401A and UAV 21401B maybe similar to UAV 21301, but may also include a flight structure 21324,which may be controlled by aviation system 21320. Flight structure 21324may be retractable and may be deployed to aid in the flight of UAV21401A and 21401B. For example, flight structure 21324 may produceadditional lift in addition to flight control surfaces 21322, e.g.,flight structure 21324 may be one or more airfoils. Additionally oralternatively, flight structure 21324 may produce additional propulsionin addition to flight control surfaces 21322. For example, flightstructure 21324 may increase a cross-sectional area and/or employ anairfoil, e.g., a sail, of UAV 21401A and/or UAV 21401B in a tailwind inorder to harness the tailwind to aid in propulsion.

UAV 21401A may deploy flight structures 21324, which may be fixed wings.The wings may enable UAV 21401A to produce more lift. Alternatively,when travelling into a headwind, or at an airspeed above a threshold, itmay be beneficial to reduce the parasitic drag of the UAV (e.g., dragassociated with movement of the UAV body through a fluid medium),therefore, the flight structures 21324 may be retracted.

UAV 21401B may deploy flight structure 21324, which may be a sail. Thesail may aid in propulsion of UAV 21401B with a tailwind. The sail maybe retracted above a certain airspeed. The airspeed for retracting thesail may be based on the airspeed of the vehicle, e.g., the drag fromthe sail may outweigh the benefits of propulsion of the sail at aparticular airspeed.

Although UAV 21401A and 21401B depict a UAV with one type of flightstructure 21324, a UAV may have multiple types of flight structures21324, e.g., including both wings and a sail.

The UAVs discussed above may include an application system 21310 thatmay interact with one or more targets. For example, the targets may beterminal devices and application system 21310 may be a mobile accesspoint that communicates with the terminal devices. Thus, there may be azone in which the mobile access node can communicate with the terminaldevices at a minimum level that may ensure some level of communication.This zone may, e.g., be based on a maximum radio range of the mobileaccess point. Within the zone, the application system should be able tointeract with each of the one or more targets at a minimum thresholdlevel.

In order to optimize the interaction between application system 21310and the one or more targets, there may be an optimal position for theUAV to be in within the zone. In the example of a mobile access point,the optimal position for the UAV may be based on providing a signalquality above a particular threshold for the terminal devices. Thethreshold may ensure a predetermined level of signal quality greaterthan that which may define the zone.

FIG. 215 shows a target location 21510 and target zone 21512. FIG. 215also depicts that a target location 21510 and target zone 21512 maychange over time. In particular, FIG. 215 depicts that a target zone21512 may increase and/or decrease over time.

As an example, UAV 21301 may have a mobile access point as anapplication system 21310. Target location 21510 may be an optimalposition for the mobile access point of application system 21310 tocommunicate with terminal devices 102 and 500. Target zone 21512 maydepict a three-dimensional zone in which the mobile access point maycommunicate with terminal devices 102 and 500 at a minimum thresholdlevel. Target zone 21512 may be defined by the location of the terminaldevices 102 and 500.

Terminal devices 102 and 500 may be mobile, e.g., they may changeposition over time. The terminal devices may remain relativelystationary, not ever translating target zone 21512, e.g., the terminaldevices may be stationary at an event, such as a sports event in astadium, or they may travel a relatively greater distance.

As shown here in solid lines, target location 21510 may be a position“p1” and at an altitude “al”. Indicated with a dashed and dotted line,terminal device 500 may change position with terminal devices 102remaining stationary. The dashed line depicts a revised target zone21512 within which the mobile access point may provide a minimumthreshold level of signal quality. Likewise, due to the revised targetzone 21512, the target location 21510 may adjust to a new position “p2”and altitude “a2”. UAV 21301 may then move to the revised targetlocation 21510.

While a UAV 21301 may communicate with a single terminal device, it maybe more efficient for a UAV 21301 to communicate with multiple terminaldevices. If a target zone 21512 has a large number of terminal devices,one or more additional UAVs 21301 may be assigned to the target zone21512 in order to reduce the communication burden of a single UAV 21301.The additional UAVs 21301 may be reassigned elsewhere if thecommunication requirements are reduced, therefore, the number of UAVs21301 in a target zone 21512 may be dynamic.

FIG. 216 shows a translational aspect of target zone 21512. At aninitial time, terminal devices 102 and 500 may be in positions definingtarget zone 21512 at a distance “d1”. The terminal devices 102 and 500may all be mobile and may all change positions by travelling to somedistance “d2”, so that the target zone 21512 is also translated to “d2”.UAV 21301 may travel within the target zone 21512, thereby tracking theterminal devices 102 and 500. Terminal devices 102 and 500 may betracked by the signal strength of communications with UAV 21301.

A target zone 21512 may also be predefined, e.g., UAV 21301 may followterminal devices along a predetermined route, e.g., a transportationroute or a parade route, such as a road, a train track, a shippingroute, a passenger flight route, among others.

Although FIG. 215 shows the boundary size of target zone 21512 changingand FIG. 216 shows translation of the target zone 21512, the target zone21512 may vary both in terms of boundary size and translation dependingon the movement of the targets, e.g., the mobile terminals.

In general, UAV 21301 may fly in the target location 21510 in order tooptimize communication quality with terminal devices 102 and 500.However, the power used for the aviation system 21320 to maintain flightin target location 21510 and the power used for the application system21310 for communications to the terminal devices 102 and 500 may exceedthe capabilities of power source 21340. A compromise position or flightpath may then be determined to match the requirements application system21310 and aviation system 21320. Additionally or alternatively, in orderto save power without degrading signal quality beyond a threshold level,UAV 21301 may adopt a different position for flight or a flight paththat required less power than the target location 21510. Additionally oralternatively, UAV 21301 may simply land within target zone 21512 andredirect all power to application system 21310, as power may no longerbe required for aviation system 21320 once the UAV 21301 has landed.

In particular, it may require more energy for UAV 21301 to fly in thetarget location 21510 when there are high winds, e.g., having a groundspeed of zero and remain relatively stationary in the air. The winds mayhave a gradient over altitude. Thus, within target zone 21512, it may bemore efficient to allow UAV 21301 to drift with a wind in a high windspeed region and then fly to a region with a lower wind speed to make upthe ground lost when drifting with the high speed wind.

Accordingly, a flight path may be determined within the target zone21512 that maintains a predetermined signal quality threshold between asignal quality level at an extreme of the target zone 21512 and a signalquality level at the target location 21510. The flight path may includea first path 21701 in which the UAV 21301 drifts with a headwind 21710that has a first velocity and a second path 21702 in which the UAV 21301heads against a headwind 21720 that has a second velocity that is lessthan the first velocity. Target location 21510 may be located alongfirst path 21701.

On first path 21701, UAV 21301 may simply drift with the wind. Forexample, UAV 21301 may have rotating wings, which may only exert enoughforce to maintain an altitude of UAV 21301 without any propulsion.Alternatively, UAV 21301 may propel itself against the wind so that theUAV 21301 drifts backwards slower than the velocity of the headwind.Along second path 21702, UAV 21301 may travel against headwind 21720.

In another example, UAV 21301 may enter the flight path when videosensing, as attempting to fly against a headwind can cause jitters inthe camera degrading the sensing quality. Therefore, by entering theflight path, the jitters may be reduced.

As shown in FIG. 217 , the entire flight path may be within target zone21512. Along first path 21701, UAV 21301 may travel from one end oftarget zone 21512 to another end and along second path 21702 travelagainst headwind 21720 again to the other end of target zone 21512. Thelength of first path 21701 and/or second path 21702 may be an entirelength of target zone 21512 or may be based on maintaining apredetermined signal quality threshold with terminal devices withintarget zone 21512, e.g., the lengths of the path may be less than anentire length of target zone 21512. As first path 21701 and second path21702 may be at different altitudes, the flight path may also include anascent path 21703 between first path 21701 and second path 21702 and adescent path 21704 between first path 21701 and second path 21702.

Drag on UAV 21301 may require a large amount of energy and power toovercome. The drag on UAV 21301 may be proportional to an airspeed ofUAV 21301. Thus, in comparison to maintaining a stationary position attarget location 21510 and fighting against headwind 21710, UAV 21301 maydrift with the headwind 21710, thus having a lower airspeed at the samealtitude as the target location 21510. Along path 21702, UAV 21301 mayfight against headwind 21720, which may have a lower velocity thanheadwind 21710, and, as long as UAV 21301 does not travel along secondpath 21702 at a velocity with an airspeed greater than that of remainingstationary at target location 21510, the overall energy output along theflight path would be less than remaining stationary at target location21510. In particular, in some cases, when the difference in altitude isless than the length of first path 21701 and/or second path 21702, theenergy output of UAV 21301 in ascending path 21303 and descending path21304 may not exceed the output savings from flying along the flightpath in comparison to remaining stationary fighting against the headwindin target location 21510.

In addition, the flight path may have a plurality of UAVs 21301cyclically travelling along it. Therefore, the rate at which a UAV 21301may pass through target location 21510 may be increased. Communicationswith a high priority or large data payload may be communicated when aUAV 21301 is in and/or around target location 21510 to ensure optimalcommunication.

In another aspect, a UAV 21301 of the plurality of UAVs 21301 maycommunicate a high priority or large data payload communication with aterminal device if the terminal device is located at a position that isnear to a UAV 21301 on the flight path. While target location 21510 maybe an optimal position for communication to all terminal devices withintarget zone 21512, communication with an individual terminal device maybe optimal at another position on the flight path.

In another aspect, second path 21702 may pass along a charging stationso that during the flight path, a UAV 21301 may land and/or dock withthe charging station in order to charge and/or refuel the power source21340. This may also be beneficial as a UAV 21301 need not expend powerfor flight to and from a charging and/or refueling station if it isgenerally in a stationary position.

To minimize power and energy output of UAV 21301, the vehicle may fly ata ground speed with a constant magnitude along first path 21701 andsecond path 21702, e.g., a negative ground speed of “x” drifting withheadwind 21710 along first path 21701 and a positive ground speed of “x”heading against headwind 21720 along second path 21702. The magnitude ofthe ground speed may be equal to one-half the difference between thefirst velocity of headwind 21710 and the second velocity of headwind21720.

This ground speed magnitude may be based on the convex relation betweendrag on an object and velocity, e.g., the relation is not linear. Thus,the average power required may be higher than the power of the averagevelocity.

In an aspect of the disclosure, assume the energy and/or power requiredto overcome drag for flight is proportional to the square of thevelocity, e.g., airspeed. Therefore, power is equal to the square of theairspeed times a constant:

P=cv ²

where P is power, c is a constant, and v is the airspeed. The averagepower spent is then proportional to:

P=P _(h) +P _(l) +P _(r) +P _(s)∝(v _(h) v _(d))²+(v _(l) +v _(d))²+α(v_(l) ² +v _(d) ²)+α(v _(h) ² +v _(d) ²)

Here, P_(h), P_(l), P_(r), and P_(s) are the powers during flight athigh altitude (first path 21701) and low altitude (second path 21702)and during rising (ascent path 21703) and sinking (descent path 21704).The first velocity of headwind 21710 may be v_(h), the second velocityof headwind 21720 may be v_(l), and the ground speed of UAV 21301 may bev_(d). The variable α takes into account the times/distances travellingvertically and horizontally differ, and is a ratio of the height(altitude) over the width (distance of first path 21701 and/or secondpath 21702):

$\alpha = \frac{h}{w}$

Airspeed is calculated by the ground speed of UAV 21301 minus the windspeed. During horizontal travel, e.g., travel along first path 21701 andsecond path 21702, the ground speed is, therefore, either added orsubtracted from the respective wind speed, depending on whethertraveling with a headwind or a tailwind. During vertical travel, thewind speed and the vertical speed are added using the Pythagoreantheorem. The power to raise the UAV 21301 against gravity is neglectedbecause this energy is later available when the UAV 21301 sinks.

Thus, in order to minimize power, the proportional relationship of thepower is considered and simplified. The derivative of this relationshipis taken to determine the minimum:

${P \propto {\left( {v_{h} - v_{d}} \right)^{2} + \left( {v_{l} + v_{d}} \right)^{2} + {\alpha\left( {v_{l}^{2} + v_{d}^{2}} \right)} + {\alpha\left( {v_{h}^{2} + v_{d}^{2}} \right)}}} = {{v_{h}^{2} + v_{l}^{2} + {2v_{l}v_{d}} - {2v_{h}v_{d}} + {2v_{d}^{2}} + {\alpha\left( {v_{l}^{2} + v_{h}^{2}} \right)} + {2\alpha v_{d}^{2}}} = {{{{2\left( {1 + \alpha} \right)v_{d}^{2}} - {2\left( {v_{h} - v_{l}} \right)v_{d}} + v_{h}^{2} + v_{l}^{2} + {{\alpha\left( {v_{l}^{2} + v_{h}^{2}} \right)}\frac{dP}{dv_{d}}}} \propto {{4\left( {1 + \alpha} \right)v_{d}} - {2\left( {v_{h} - v_{l}} \right)}}} = 0}}$$v_{d} = {\frac{v_{h} - v_{l}}{2 + {2\alpha}} = {\frac{v_{h} - v_{l}}{2 + {2h/w}} = {\frac{\left( {v_{h} - v_{l}} \right)}{2}\frac{w}{w + h}}}}$

Thus, for the case in which h may be neglected in relation to w, theoptimum ground speed may be the average of the first velocity ofheadwind 21710 and the second velocity of headwind 21720, because theairspeed of UAV 21301 may be equal on first path 21701 and second path21702. Due to the convex relationship of power and velocity, this mayensure the least average power. If h may not be neglected, then theoptimal ground speed of UAV 21301 may be lower, because the powerrequired for ascent and descent also need to be considered. Tus it maybe best to accept a higher average power on the horizontal legs toreduce the power needed on the vertical legs.

In another aspect of the disclosure, assume the energy and/or powerrequired to overcome drag for flight is proportional to the cube of thevelocity, e.g., airspeed. Therefore, power is equal to the cube of theairspeed times a constant:

P=cv ³

where P is power, c is a constant, and v is the airspeed. The averagepower spent is then proportional to:

$P = {{P_{h} + P_{l} + P_{r} + P_{s}} \propto {\left( {v_{h} - v_{d}} \right)^{3} + \left( {v_{l} + v_{d}} \right)^{3} + {\alpha{\sqrt{v_{l}^{2} + v_{d}^{2}}}^{3}} + {\alpha{\sqrt{v_{h}^{2} + v_{d}^{2}}}^{3}}}}$

Here, P_(h), P_(l), P_(r), and P_(s) are the powers during flight athigh altitude (first path 21701) and low altitude (second path 21702)and during rising (ascent path 21703) and sinking (descent path 21704).The first velocity of headwind 21710 may be v_(h), the second velocityof headwind 21720 may be v_(l), and the ground speed of UAV 21301 may bev_(d). The variable α takes into account the times/distances travellingvertically and horizontally differ, and is a ratio of the height(altitude) over the width (distance of first path 21701 and/or secondpath 21702):

$\alpha = \frac{h}{w}$

Airspeed is calculated by the ground speed of UAV 21301 minus the windspeed. During horizontal travel, e.g., travel along first path 21701 andsecond path 21702, the ground speed is, therefore, either added orsubtracted from the respective wind speed, depending on whethertraveling with a headwind or a tailwind. During vertical travel, thewind speed and the vertical speed are added using the Pythagoreantheorem. The power to raise the UAV 21301 against gravity is neglectedbecause this energy is later available when the UAV 21301 sinks.

Thus, in order to minimize power, the proportional relationship of thepower is considered and simplified. The derivative of this relationshipis taken to determine the minimum:

P ∝ (v_(h) − v_(d))³ + (v_(l) + v_(d))³ + α(v_(l)² + v_(d)²)^(3/2) + α(v_(h)² + v_(d)²)^(3/2)${\frac{dP}{{dv}_{d}} \propto {{{- 3}\left( {v_{h} - v_{d}} \right)^{2}} + {3\left( {v_{l} + v_{d}} \right)^{2}} + {\frac{3}{2}\alpha\sqrt{v_{l}^{2} + v_{d}^{2}}} + {\frac{3}{2}\alpha\sqrt{v_{h}^{2} + v_{d}^{2}}}}} = 0$${{- \left( {v_{h} - v_{d}} \right)^{2}} + \left( {v_{l} + v_{d}} \right)^{2} + {\frac{1}{2}\alpha\sqrt{v_{l}^{2} + v_{d}^{2}}} + {\frac{1}{2}\alpha\sqrt{v_{h}^{2} + v_{d}^{2}}}} = 0$

This equation may be difficult to consider in closed form, accordingly,a simplification with α=0 results in:

−(v _(h) −v _(d))²+(v _(l) +v _(d))²=0

(v _(h) −v _(d))²=(v _(l) +v _(d))²

(v _(h) −v _(d))=±(v _(l) +v _(d))

(v _(h) −v _(d))=±(v _(l) +v _(d))

Assuming the positive result is the minimum:

$v_{d} = \frac{v_{h} - v_{l}}{2}$

Again, this result minimizes the power of a convex function, and againif α≠0, correction terms may need to be considered, which would reducev_(d).

In another aspect of the disclosure, power may be assumed to be thesquare of the difference to an optimal speed plus a constant, e.g.,assume a Taylor expansion around the minimum and only consider thesquare component.

Thus, power consumption of a fixed wing aircraft may be approximated bya power law such as:

P=P ₀ +c(v−v ₀)²

with suitable constants c, P₀, and v₀, where v is the airspeed and v₀ isthe airspeed requiring at least power P₀. The average power expended isthen proportional to:

P=P _(h) +P _(l) +P _(r) +P _(s) ∝P ₀ /c+(v _(h) −v _(d) −v ₀)²+(v _(l)+v _(d) −v ₀)²+α(√{square root over ((v _(l) ² +v _(d) ²))}−v₀)²+α(√{square root over ((v _(h) ² +v _(d) ²))}−v ₀)²

Here, P_(h), P_(l), P_(r), and P_(s) are the powers during flight athigh altitude (first path 21701) and low altitude (second path 21702)and during rising (ascent path 21703) and sinking (descent path 21704).The first velocity of headwind 21710 may be v_(h), the second velocityof headwind 21720 may be v_(l), and the ground speed of UAV 21301 may bev_(d). The variable α takes into account the times/distances travellingvertically and horizontally differ, and is a ratio of the height(altitude) over the width (distance of first path 21701 and/or secondpath 21702):

$\alpha = \frac{h}{w}$

Airspeed is calculated by the ground speed of UAV 21301 minus the windspeed. During horizontal travel, e.g., travel along first path 21701 andsecond path 21702, the ground speed is, therefore, either added orsubtracted from the respective wind speed, depending on whethertraveling with a headwind or a tailwind. During vertical travel, thewind speed and the vertical speed are added using the Pythagoreantheorem. The power to raise the UAV 21301 against gravity is neglectedbecause this energy is later available when the UAV 21301 sinks.

In order to minimize the power, it is then calculated:

${P \propto {\frac{P_{0}}{c} + \left( {v_{h} - v_{d} - v_{0}} \right)^{2} + \left( {v_{l} + v_{d} - v_{0}} \right)^{2} + {\alpha\left( {\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)} - v_{0}} \right)}^{2} + {\alpha\left( {\sqrt{\left( {v_{h}^{2} + v_{d}^{2}} \right)} - v_{0}} \right)}^{2}}} = {{\frac{P_{0}}{c} + v_{h}^{2} + v_{l}^{2} + {2v_{l}v_{d}} - {2v_{h}v_{d}} - {v_{h}v_{0}} - {v_{l}v_{0}} + {2v_{d}^{2}} + {2v_{0}^{2}} + {\alpha\left( {v_{l}^{2} + v_{h}^{2}} \right)} + {2\alpha v_{d}^{2}} + {2\alpha v_{0}^{2}} - {2\alpha v_{0}\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)}} - {2\alpha v_{0}\sqrt{\left( {v_{h}^{2} + v_{d}^{2}} \right)}}} = {{2\left( {1 + \alpha} \right)v_{d}^{2}} - {2\left( {v_{h} - v_{l}} \right)v_{d}} - {2\alpha v_{0}\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)}} - {2\alpha v_{0}\sqrt{\left( {v_{h}^{2} + v_{d}^{2}} \right)}} + {{constant}\left( v_{d} \right)}}}$

In order to make this formula tractable, (v_(l) ²+v_(d) ²) is developedinto a Taylor series with v_(d):

$\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)} = {{{v_{l} + {\frac{1}{2}{v_{d}^{2}\left\lbrack \frac{d^{2}\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)}}{{dv}_{d}^{2}} \right\rbrack}_{v_{d} = 0}} +}...} = {{{v_{l} + {\frac{1}{2}{v_{d}^{2}\left\lbrack {\frac{d}{v_{d}}\left( {\frac{1}{2}\frac{1}{\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)}}2v_{d}} \right)} \right\rbrack}_{v_{d} = 0}} +}...} = {{{v_{l} + {\frac{1}{2}{v_{d}^{2}\left\lbrack \left( \frac{\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)} - {v_{d}\frac{1}{2\sqrt{\left( {v_{l}^{2} + v_{d}^{2}} \right)}}}}{\left( {v_{l}^{2} + v_{d}^{2}} \right)} \right) \right\rbrack}_{v_{d} = 0}} +}...} = {{{v_{l} + {\frac{1}{2}{v_{d}^{2}\left\lbrack \frac{1}{v_{l}} \right\rbrack}} +}...} = {{v_{l} + \frac{v_{d}^{2}}{2v_{l}} +}...}}}}}$

This is simplified to:

$P \propto {{2\left( {1 + \alpha} \right)v_{d}^{2}} - {2\left( {v_{h} - v_{l}} \right)v_{d}} - {\alpha v_{0}\frac{v_{d}^{2}}{v_{l}}} - {\alpha v_{0}\frac{v_{d}^{2}}{v_{h}}} + {{constant}\left( v_{d} \right)}}$$v_{d} = {\frac{v_{h} - v_{l}}{2 + {2\alpha} - \frac{\alpha v_{0}}{v_{l}} - \frac{\alpha v_{0}}{v_{h}}} = \frac{v_{h} - v_{l}}{2 + {{2}^{h}/{w\left( {1 - \frac{\alpha v_{0}}{2v_{l}} - \frac{\alpha v_{0}}{2v_{h}}} \right)}}}}$

Taking the derivative to find the minimum:

${\frac{dP}{{dv}_{d}} \propto {{2\left( {2 + {2\alpha} - \frac{\alpha v_{0}}{v_{l}} - \frac{\alpha v_{0}}{v_{h}}} \right)v_{d}} - {2\left( {v_{h} - v_{l}} \right)}}} = 0$$v_{d} = {\frac{v_{h} - v_{l}}{2 + {2\alpha} - \frac{\alpha v_{0}}{v_{l}} - \frac{\alpha v_{0}}{v_{h}}} = \frac{v_{h} - v_{l}}{2 + {{2}^{h}/{w\left( {1 - \frac{v_{0}}{2v_{l}} - \frac{v_{0}}{2v_{h}}} \right)}}}}$

This result may be similar to a pure square law, but includes a modifiedcorrection term in the denominator. The modified correction term may bedependent on the height to width ratio and the wind speed relative tothe optimum speed. If v₀=0, then the formula simplifies to that of apure square law. Similarly, if v₀ is much greater than v_(l) and v_(h),then the formula may also simplify to that of a pure square law.Otherwise, the optimum speed may be higher, which is because at v₀(instead of at a speed of zero) the minimum power is achieved. This mayresult from the power required to ascend and descend on the verticallegs against the induced air drag, which may be assumed to be less inthis model in comparison to the pure square law.

This assumption may be reasonable as a rotating wing aircraft maygenerate lift by pushing down surrounding air, thus passing downward animpulse from the weight of the aircraft to the air. As the rotor coversa given area the volume of air being pushed downwards is proportional tothis area A and the speed of the downward movement of the air isdesignated s. The mass being pushed down per second is proportional tothe volume of the air times the air density p. The impulse imparted tothe air comes from the acceleration of the mass of the air from a speedof zero to the final downward speed s. This change of impulse over timemay be proportional to the lift force F:

$F = {\frac{d{Impulse}}{dt} = {{m*\frac{\Delta v}{\Delta t}} = {{\rho{As}*s} = {\rho{As}^{2}}}}}$

Solving for s, the equation is:

$s = \sqrt{\frac{F}{\rho A}}$

The energy required to accelerate the air to speed s may be ½ ms², andthus, the power P may be:

$P = {\frac{\frac{1}{2}{ms}^{2}}{t} = {{\frac{1}{2}\frac{m}{t}*s^{2}} = {{\frac{1}{2}\rho{As}*s^{2}} = {{\frac{1}{2}\rho{As}^{3}} = {{\frac{1}{2}\rho A{\sqrt{\frac{F}{\rho A}}}^{3}} = {{\frac{1}{2}\sqrt{\frac{F^{3}}{\rho A}}} \propto F^{3/2}}}}}}}$

The power may be proportional to the force to the power of 3/2, e.g.,slightly more than linear. The required force may depend on thedetermined flight path, while the remaining factors may be constant forany given UAV (A) at a given location (ρ).

The force F may include the weight of the UAV F_(g) and the air dragF_(d), which may typically increase with the square of the airspeed,F_(d)=βv_(air) ². Therefore, the required power may depend on the totalforce need, which may be the vector addition of F_(g) and F_(d). Ifhorizontal movement is assumed, then F_(g)⊥F_(d), which may result in:

$F = {{{\sqrt{F_{g}^{2} + F_{d}^{2}}{and}P} \propto {\sqrt{F_{g}^{2} + F_{d}^{2}}}^{\frac{3}{2}}} = {\left( {F_{g}^{2} + F_{d}^{2}} \right)^{\frac{3}{4}} = \left( {F_{g}^{2} + {\beta^{2}v_{air}^{4}}} \right)^{3/4}}}$

Otherwise, for vertical travel, then F_(g)∥F_(d) and F=F_(g)±F_(d), withselection of the positive or negative component depending on whether theforces are in the same or opposite direction, resulting in:

$F = {{{F_{g} \pm {F_{d}{and}P}} \propto {\sqrt{F_{g} \pm F_{d}}}^{3}} = {\sqrt{F_{g} \pm {\alpha v_{air}^{2}}}}^{3}}$

In total, the required power is proportional to:

P = P_(h) + P_(l) + P_(r) + P_(s)∝$P \propto {\left( {F_{g}^{2} + {\beta^{2}\left( {v_{h} - v_{d}} \right)}^{4}} \right)^{\frac{3}{4}} + \left( {F_{g}^{2} + {\beta^{2}\left( {v_{l} + v_{d}} \right)}^{4}} \right)^{\frac{3}{4}} + {\sqrt{F_{g} + {\beta v_{d}^{2}}}}^{3} + {\sqrt{F_{g} - {\beta v_{d}^{2}}}}^{3}}$

Thus, it may generally be observed that if h is negligible against w,then the ground speed of the UAV 21301 may be half the difference of thewind speeds. In this case, the speed against the wind may be the same onthe first path 21701 as on the second path 21702, which may minimize thetotal or average power (assuming power and velocity has a convexrelationship).

If, however, w is negligible in comparison to h, then the UAV groundspeed may tend to 0, as it may require too much output to movevertically. In intermediate cases the ground speed of UAV 21301 may bereduced with one-half the difference of the first velocity of headwind21710 and the second velocity of headwind 21720.

In comparison to the flight path depicted in FIG. 217 , the flight pathin FIG. 218 may have a rounded rather than rectangular profile. In firstpath 21801 and second path 21802, UAV 21301 may have require less outputto head against a headwind. First path 21801 and 21802 may be withintarget zone 21512.

During first path 21801, UAV 21301 may drift with a headwind 21710 andduring second path 21802, UAV 21301 may head against a headwind 21720.Headwind 21710 may have a greater velocity along any point of first path21801 than the velocity of headwind 21720 along any point of second path21802. For example, during ascent path 21703, UAV 21301 is fightingagainst the gradient of the headwind, so that UAV 21301 may at somepoint be ascending and countering the headwind to have a ground speed ofzero, which requires a greater output than drifting with the headwind.Therefore, in the ascending and descending phases of first path 21801and second path 21802, UAV 21301 may require less output to counter aheadwind. At no point along first path 21801 and second path 21802should UAV 21301 achieve a ground speed of zero at the same altitude asthe target location 21510. Second path 21802 may transition into firstpath 21801 at the midpoint of the minimum altitude of 21802 and themaximum altitude 21801. Additionally or alternatively, the transitionpoint may be selected at a predetermined altitude. The predeterminedaltitude may be based on the energy and/or power output required to headagainst or drift with the wind.

Similar to a rounded profile, UAV 21301 may travel a trapezoidal profileor other non-rectangular profile so that when UAV 21301 is ascendinginto higher velocity winds, it need not counter the headwind to maintaina groundspeed of zero. Therefore, first path 21801 may have a profilewith a section that is slanted and rising to a section with a constantaltitude and again a final section slanted and falling, while the secondpath 21802 may have a vertical descent and a vertical ascent connectedby a constant altitude horizontal section. Second path 21802 maytransition into first path 21801 at the midpoint of the minimum altitudeof 21802 and the maximum altitude 21801. Additionally or alternatively,the transition point may be selected at a predetermined altitude. Thepredetermined altitude may be based on the energy and/or power outputrequired to head against or drift with the wind.

In comparison to the flight paths in FIG. 217 and FIG. 218 , the flightpath in FIG. 219 may be at the same altitude or an altitude within anegligible altitude difference, which may be indicated by the axes x andy, with altitude the axis perpendicular to the x-y plane. Thedifferential wind velocities may be due to aerodynamic effects overground surfaces or other objects. For example, wind deflecting around anobject may accelerate the air (jet effect), which may be exploited byUAV 21301.

Therefore, UAV 21301 may drift with a headwind 21910 that has a firstvelocity in a first path 21901 and may head against a headwind 21920that has a second velocity less than the first velocity. First path21901 and second path 21902 may be within target zone 21512. First path21901 may be at a substantially similar altitude as second path 21902.To reach the first path 21901 and the second path 21902, UAV 21301 mayfly along connecting paths 21903. Alternatively, first path 21901 andsecond path 21902 may have a non-rectangular flight profile, such as therounded or trapezoidal vertical flight profile discussed above, althoughhere, the flight profile may be considered on an x-y plane with at onealtitude or substantially similar altitudes.

In addition, UAV 21301 may fly along a flight path that may vary in bothaltitude and in the x-y plane so that the flight path may includeaspects of the flight paths in FIG. 217 and FIG. 218 , as well as FIG.219 .

Method 22000 may be a method of flying an unmanned aerial vehicle (UAV)21301 for station-keeping relative to a target zone, the method mayinclude: determining a target zone 21512 based on one or more targets;determining a flight path for the UAV 21301 within the target zone21512, the flight path including: a first path 21701 in which the UAV21301 drifts with a headwind 21710 that has a first velocity and asecond path 21702 in which the UAV 21301 heads against a headwind 21720that has a second velocity that is less than the first velocity; andflying the UAV 21301 along the flight path.

The UAV 21301 may include an application system 21310, which may includea mobile access point 110 and/or may include a sensing system. The oneor more targets may change location over time.

Method 22000 may further include operating the application system 21310with the one or more targets. The target zone 21512 may be based on amaximum range of the application system 21310 operating with the one ormore targets. The target zone 21512 may further include a targetlocation 21510 based on an optimal range of the application systemoperating with the one or more targets.

Method 22000 may further include flying the UAV 21301 along the firstpath 21701 with a ground speed based on one-half the difference of thefirst velocity and the second velocity. The first path 21701 may be afirst attitude and the second path 21702 may be at second altitude lowerthan the first altitude. The flight path may include an ascent path tothe first altitude and a descent path to the second altitude. The flightpath may have a charging and/or refueling station located along theflight path. The functions of method 22000 may also be performed by themeans described above in relation to UAV 21301.

Method 22100 may be a method of flying an unmanned aerial vehicle (UAV)21301 including a mobile access point 110 along a flight path, themethod including: determining a target zone 21512 based on one or moreterminal devices 102 and/or 500 that are configured to communicate withthe mobile access point 110; determining a flight path for the UAVwithin the target zone 21512, the flight path including: a first path21701 in which the UAV 21301 drifts with a headwind 21710 that has afirst velocity and a second path 21702 in which the UAV 21301 headsagainst a headwind 21720 that has a second velocity that is less thanthe first velocity; and flying the UAV 21301 along the flight path.

The target zone 21512 may be based on a maximum communication range ofthe mobile access point 110. The target zone may be based on acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. Target Zone 21512 may further include atarget location 21510 based on a predefined threshold of a communicationquality parameter threshold for communications with the one or moreterminal devices 102 and/or 500. The communication quality parameter maybe based on a signal strength indicator and/or a signal qualityindicator. The one or more terminal devices may change locationovertime, and thus, the target zone 21512 may change shape and/orposition over time.

In method 22100, the UAV 21301 may be flown along the flight path with aground speed based on one-half the difference of the first velocity andthe second velocity. The first path 21701 may be at a first altitude andthe second path 21702 may be at a second altitude lower than the firstaltitude. The flight path may further include an ascent path 21703 tothe first altitude and a descent path 21704 to the second altitude. Thefirst path 21701 and/or the second path 21702 may have a greaterhorizontal distance than a vertical distance of the ascent path 21703and/or the descent path 21704. A charging station may be located alongthe flight path. Method 22100 may further include communicating with theone or more terminal devices 102 and/or 500 in the target zone 21512.The functions of method 22100 may also be performed by the meansdescribed above in relation to UAV 21301.

An unmanned aerial vehicle (UAV), e.g., UAV 21301, may include anapplication system 21310 including a mobile access point 110 configuredto communicate with one or more terminal devices 102 and/or 500; aprocessor 21330 configured to: determine at target zone 21512 based onthe one or more terminal devices 102 and/or 500; determine a flight pathfor the UAV within the target zone 21512, the flight path including: afirst path 21701 for the UAV in which the UAV drifts with a headwind21710 that has a first velocity and a second path 21702 in which the UAVheads against a headwind 21720 that has a second velocity that is lessthan the first velocity; and an aviation system 21320 configured to flythe UAV along the flight path.

The target zone 21512 may be based on a maximum communication range ofthe mobile access point 110. The target zone 21512 may be based on acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. Target Zone 21512 may further include atarget location 21510 based on a predefined threshold of a communicationquality parameter threshold for communications with the one or moreterminal devices 102 and/or 500. The communication quality parameter maybe based on a signal strength indicator and/or a signal qualityindicator. The one or more terminal devices may change locationovertime, and thus, the target zone 21512 may change shape and/orposition over time.

The aviation system 21320 may be configured to fly the UAV along theflight path with a ground speed based on one-half the difference of thefirst velocity and the second velocity. The first path 21701 may be at afirst altitude and the second path 21702 may be at a second altitudelower than the first altitude. The flight path may further include anascent path 21703 to the first altitude and a descent path 21704 to thesecond altitude. The first path 21701 and/or the second path 21702 mayhave a greater horizontal distance than a vertical distance of theascent path 21703 and/or the descent path 21704. A charging station maybe located along the flight path. Application system 21320 maycommunicate with the one or more terminal devices 102 and/or 500 in thetarget zone 21512. The UAV may include a flight structure 21324configured to be extended or retracted based on an airspeed of the UAV.

In another aspect of the disclosure, a plurality of UAVs 21301 mayreduce aviation system 21320 requirements by flying in a flightformation, as shown in FIG. 222 , which may allow for more allocation ofpower source 21340 to application system 21310. The flight formation mayreduce an aviation system load on a particular UAV 21301. For example,the drag on a UAV 21301 in the flight formation may be reduced and/or aUAV 21301 may benefit from upwash in the flight formation. Upwash may bean upward motion of air due to airflow over an airfoil.

The flight formation and the position of a UAV 21301 in the flightformation may be based on application system 21310 consumptionrequirements and aviation system requirements 21320 from power source21340 of a UAV 21301. Therefore, for a particular UAV 21301 of theplurality of UAVs 21301, the individual application system 21310 energyconsumption requirement may be determined and the individual aviationsystem 21320 energy consumption requirement may be determined. Theapplication system 21310 energy consumption requirement may be based onthe instantaneous, e.g., at a particular time, and/or expected orestimated energy consumption of the application system 21310. The energyconsumption may, for example, be based on a number of terminal devicescommunicating with a mobile access point of application system 21310.Additionally or alternatively, the energy consumption may, for example,be based on a type of communication with one or more terminal devices.Thus, a type of communication may require a higher data rate or aconstant connection, e.g., video or audio streaming in comparison todata for e-mail or loading a webpage. In addition, various applicationsystems 21310 of a UAV 21301 may have differing energy consumptionrequirements. For example, an application system 21310 for communicationwith terminal devices may be different than an application system 21310for sensing, e.g., sensing with local sensors (e.g., audio, video,image, position, radar, light, environmental, or any other type ofsensing component) to obtain sensing data.

The aviation system 21320 energy consumption requirements may bedetermined instantaneously, e.g., at a particular time, or may be anexpected or estimated. The aviation system 21320 energy consumptionrequirements may be based on the power required for flight of UAV 21301.For example, various UAVs 21301 may have different weights; a heavierUAV may require more power for aviation than a lighter UAV. Additionallyor alternatively, various UAVs 21301 may utilize different flightcontrol surfaces 21322, so that a particular UAV 21301 may require ahigher energy consumption for flight than another UAV 21301 with adiffering flight control surface system 21322.

Accordingly, the individual application system 21310 requirements forthe plurality of UAVs 21301 may be determined and the individualaviation system 21320 requirements for the plurality of UAVs 21301 mayalso be determined. The individual UAVs 21301 may then be ranked onenergy consumption requirements based on the determined information.

A flight formation may then be determined based on the energyconsumption requirements. The flight formation may include a UAV 21301with the lowest application system 21310 energy consumption requirementflying in a position 22210 of the flight formation requiring the highestaviation system 21320 energy consumption requirement. Therefore, the UAV21301 with the lowest application system 21310 energy consumptionrequirement may allocate more power to its aviation system 21320.

The position 22210 may be a lead position in the flight formation. TheUAV 21301 in the position 22210 may have the highest drag position inthe flight formation, and may require then the greatest output of energyfor its aviation system 21320.

The other UAVs 21301 may then be placed in a position 22220 in theflight formation. Position 22220 may be a secondary position or a“wingman” position. The UAV 21301 in a position 22220 may benefitaerodynamically from its position relative to the UAV 21301 in position22210. For example, the UAV 21301 in position 22220 may experiencereduced drag behind a UAV 21301 in position 22210 by drafting orremaining in the slipstream of the UAV 21301 in position 22210.Furthermore, the UAV 21301 in position 22220 may receive a lift forcefrom upwash of the UAV 21301 in position 22210. The plurality of UAVs21301 may communicate with each other to maintain the flight formation,as may be shown by the dashed line.

As shown in FIG. 222 , UAV 21301 in position 22210 may require thegreatest energy output for its aviation system 21320. For example,position 22210 may be a lead position flying into a headwind 22200. TheUAV 21301 in position 22210 may be communicating with a single terminaldevice 102.

The UAV 21301 in position 22220 may benefit aerodynamically from itsposition relative to UAV 21301 in position 22210, and may have a higherapplication system 21310 energy consumption requirement than the UAV21301 in position 22210. For example, The UAV 21301 in position 22220may be communicating with a terminal device 102 and a terminal device500.

The plurality of UAVs 21301 may determine the energy consumptionsrequirements of the individual UAVs 21301 cooperatively by communicatingamongst themselves, as well as determining the flight formation.Alternatively, the plurality of UAVs 21301 may have a lead UAV 21301 oran external flight formation controller that may be designated todetermine the individual energy consumption requirements and the flightformation. For example, the individual UAVs 21301 may transmitmeasurements or the determined energy consumption requirements and thenmay receive a designated position in the flight formation.

FIG. 223 shows an exemplary flight formation of UAVs 21301. The UAV21301 in position 22310 may require the greatest energy consumption forits aviation system 21320, for example, flying in the lead position intoa headwind 22300, and the least energy consumption for communicatingwith terminal device 102. UAV 21301 in position 22310 may have a unicastcommunication configuration with terminal device 102.

The UAVs 21301 in positions 22320 may have a reduced energy consumptionfor their respective aviation systems 21320 in comparison with UAV 21301in position 22310, but an increased energy consumption for theirrespective applications systems 21310 in comparison with UAV 21301 inposition 22310. For example, the second UAV 21301 in position 22320directly behind position 22310 may have a multicast communicationconfiguration with two terminal devices 102 and a terminal device 500.The fourth and final UAV 21301 in position 22320 may have a unicastcommunication configuration with two terminal devices 102.

UAV 21301 in position 22330 may be tasked with measurement and sensingfor the plurality of UAVs 21301 in the flight formation. Thus, UAV 21301in position 22330 may perform sensing and measurements that are thentransmitted to the other UAVs 21301 in the flight formation.

Although the UAVs 21301 in FIG. 223 are depicted as having distincttasks, e.g., communications, measurements, and/or sensing, multipletasks may be performed by a single UAV 21301 in the flight formation. Inaddition, the positions of the UAVs 21301 in the flight formation arenot fixed, but may be adjusted dynamically based on varying energyconsumption requirements.

FIG. 224 shows an exemplary flight formation. The plurality of UAVs21301 may be in a “flying-v” formation. A UAV 21301 may be in a position22410 leading the plurality of UAVs 21301. Positions 22420 may be filledwith the other UAVs 21301 of the plurality of UAVs 21301, which may beslightly behind and laterally offset from each other in order to benefitfrom the upwash of another UAV 21301 slightly ahead and laterally offsetfrom it.

Method 22500 may include a method of controlling a flight formation of aplurality of unmanned aerial vehicles (UAVs) 21301 each including anapplication system 21310, an aviation system 21320, and a power source21340, the method including: determining individual application system21310 energy consumption requirements for the plurality of UAVs 21301;determining individual aviation system 21320 energy consumptionrequirements for the plurality of UAVs 21301; determining a flightformation for the plurality of UAVs 21310, the flight formationcomprising a UAV 21301 with the lowest application system 21310 energyconsumption requirement flying in a position of the flight formationrequiring the highest aviation system 21320 energy consumptionrequirement; and arranging the plurality of UAVs 21301 in the flightformation.

Method 22500 may include adjusting positions of the plurality of UAVs21301 within the flight formation based on changing individualapplication system energy consumption requirements of the plurality ofUAVs 21301. The applications system may include a mobile access point21310 and/or a sensing system. The flight formation may include theplurality of UAVs 21301 in a line in a direction of flight. The flightformation may include the plurality of UAVs 21301 in a V-shape. Thefunctions of method 22500 may also be performed by the means describedabove in relation to UAV 21301.

A flight formation controller for a plurality of unmanned aerialvehicles (UAVs) each comprising an application system 21310, an aviationsystem 21320, and a power source 21340, the flight formation controllercomprising: a receiver configured to receive individual applicationsystem 21310 energy consumption requirements for the plurality of UAVs21301 and individual aviation system 21320 energy consumptionrequirements for the plurality of UAVs 21301; a processor configured todetermine a flight formation for the plurality of UAVs 21301, the flightformation comprising a UAV 21301 with the lowest application system21310 energy consumption requirement flying in a position of the flightformation requiring the highest aviation system 21320 energy consumptionrequirement; and a transmitter to send information indicating the flightformation to the plurality of UAVs 21301.

The controller of the flight formation controller may be configured toadjust positions of the plurality of UAVs 21301 within the flightformation based on changing individual application system energyconsumption requirements of the plurality of UAVs 21301. Theapplications system may include a mobile access point 21310 and/or asensing system. The flight formation may include the plurality of UAVs21301 in a line in a direction of flight. The flight formation mayinclude the plurality of UAVs 21301 in a V-shape.

An unmanned aerial vehicle (UAV) may include: an aviation system 21320configured to control flight of the UAV; an application system 21310comprising an application device, the application system configured tocontrol the application device; a power source 21340 configured toprovide energy for the aviation system 21320 and the application system21310; a transmitter to send individual application system 21310 energyconsumption requirements for the UAV and individual aviation system 72energy consumption requirements for the UAV; a receiver configured toreceive information indicating a flight formation for a plurality ofUAVs that includes the UAV, with the flight formation comprising a UAVwith the lowest application system 21310 energy consumption requirementflying in a position of the flight formation requiring the highestaviation system 21320 energy consumption requirement; and the aviationsystem 21320 further configured to control the UAV to take position inthe flight formation based on the information indicating the flightformation.

The receiver may be further configured to receive an indication toadjust position of the UAV within the flight formation based on changingindividual application system 21310 energy consumption requirements ofthe plurality of UAVs. The application device may include a mobileaccess point 110 and/or a sensing system. The flight formation mayinclude the plurality of UAVs 21301 in a line in a direction of flight.The flight formation may include the plurality of UAVs 21301 in aV-shape.

In another aspect of the disclosure a UAV 21301 may be configured as arelay 22601 for a network access node 22610, which is shown in FIG. 226. Network access node 22610 may be substantially the same or similar tonetwork access node 110, but may additionally be configured tocommunicate with a relay 22601, which may be a UAV 21301.

The UAV 21301 may track a terminal device 102, e.g., within a targetzone 21512, so that terminal device 102 may remain connected whenleaving a cell of network access node 22610, e.g., it may not require ahandover when leaving the cell. The handover may effectively be shiftedto a different level of network hierarchy.

Thus, in some cases, the handover is less critical from the point ofview of terminal device 102. UAV 21301, configured as a relay 22601,(relay 22601 and UAV 21301 may be used interchangeably for this aspectof the disclosure) may establish communication with terminal device 102,while the terminal device 102 is being served by network access node22610 until the terminal device 102 travels a predefined distance orenters coverage of another network access node. Relay 22601 may thusbridge a critical area in a gap (e.g., no man's land) between stationarynetwork access nodes.

Thus, a relay 22601 may initially be positioned at an edge or borderarea of the coverage of network access node 22610, where they may beready for a handover of a terminal device 102, e.g., from network accessnode 22610 to relay 22601. As an example, the relay 22601 may trackterminal devices 102 and/or 500, which may travel along predeterminedroutes, e.g., train tracks or roads, etc., and may bridge a gap betweennetwork access nodes, and afterwards return to a position awaitinganother terminal device 102 and/or 500 to travel along the route. Therelay may, for example, remain stationary in position, or follow a lowerenergy consumption flight path as discussed above, or may land at acharging and/or refueling station 22640 along the predetermined route.

As may be shown in FIG. 226 , a terminal device 102 may be within acoverage area 22612 of a network access node 22610. Terminal device 102may be communicating with network access node 22610. Relay 22601 mayalso be communicating with network access node 22610. As terminal device102 nears the edge of coverage area 22612, UAV 21301 may be configuredas a relay 22601 between terminal device 102 and network access node22610. For example, UAV 21301 may be in a better position to communicatewith network access node 22610 and/or have a mobile access point 110that may have a more powerful transceiver compared to terminal device102. Additionally or alternatively, relay 22601 may communicate with thenetwork via other network access nodes.

As terminal device 102 leaves the coverage area 22612, relay 22601 maymaintain communication with terminal device 102 and track it, e.g.,relay 22601 may remain within a target zone 21512 of terminal device102. From the point of view of terminal device 102, it is still withinthe coverage area 22612 of network access node 22610, as it has not beenrequired to execute a handover to another network access node 22610.

An exemplary handover is shown in FIG. 227 . Terminal device 102 mayinitially be in coverage area 22612 of network access node 22610. Relay22601 may be hovering in an energy efficient location, may be chargingand/or refueling at a station 22640, or may be landed.

Terminal device 102 may move to an edge of coverage area 22612.

In anticipation of a handover, relay 22601 may move towards terminaldevice 102 if not already positioned nearby or within communicationrange. Relay 22601 may communicate with network access node 22610 inpreparation of handover of the terminal device 102 from directcommunication with the network access node 22610 to relay 22601.

Terminal device 102 may be handed over to relay 22601, which forwardsdata between the terminal device 102 and network access node 22610.

The terminal device 102 may then move out of coverage area 22612, butmay remain in communication with relay 22601. Relay 22601 is incommunication with network access node 22610.

Terminal device 102 may move closer to network access node 22620 and itscoverage area 22622. Relay 22601 may track terminal device 102, e.g.,flying within a target zone 21512 based on terminal device 102 (or aplurality of terminal devices 102 and/or 500), and may continuecommunications with network access node 22610.

When close enough to network access node 22620, relay 22601 hands overfrom network access node 22610 to network access node 22620 and nowforwards data between terminal device 102 and network access node 22620.At this point, terminal device 102 still does not experience a handover.

Terminal device 102 may enter an edge area of coverage area 22622, butmay remain in communication with relay 22601. Upon reaching a certainthreshold level signal from network access node 22620, terminal device102 may finally hand over to network access node 22620 and disengagefrom relay 22601.

Relay 22601 may move to an energy efficient position, fly and/or land ina position to track another terminal device, or fly to a charging and/orrefueling station 22640. Alternatively, relay 22601 may return to aposition within network access node 22610.

In an aspect of the disclosure, there may be a plurality of UAVs 21301configured as relays 22601 that may travel between network access nodestracking terminal devices. After functioning as a relay 22601 for aterminal device, relay 22601 may fly to another network access node thathas no UAVs 21301 or requires more.

The network may control the execution of handovers and dispatch of UAVs21301 configured as relays 22601. Relay 22601 may communicateinformation relating to location and status of both terminal devices andother UAVs 21301. Additionally or alternatively, a relay 22601 may beconfigured to control the execution of a handover, or another networksystem may receive the information relating to location and statuses andcontrol the handovers, e.g., at a charging and/or refueling station22640, which may function as a control unit or dispatcher.

The handovers may reuse legacy signaling to effect the handovers fromnetwork access nodes 22610 and 22620 and relay 22601, e.g., relay nodesin LTE-A. For example, the X2 interface may be reused (or the X2interface via the mobile access point 110 in the relay 22601) foradministrating handovers and for measurements related to terminal device102. Handover criteria such as signal strength indicators, e.g.,received signal strength indicator (RSSI), and/or signal qualityindicators, e.g., signal-to-noise ratio (SNR),signal-to-interference-plus-noise ratio (SINR), reference signalreceived quality (RSRQ), reference signal received power (RSRP), etc.,may also be used for handovers from network access nodes 22610 and 22620to and from relay 22601.

Method 22800 may be a method of flying an unmanned aerial vehicle (UAV)21301 including a mobile access point 110 along a flight path, themethod 22800 including: configuring the mobile access point 110 as arelay 22601 for a network access node 22610 and to communicate with oneor more terminal devices 102 and/or 500; handing over communication ofthe one or more terminal devices 102 and/or 500 from the network accessnode 22610 to the mobile access point 110; determining a target zone21512 based on the one or more terminal devices 102 and/or 500;determining a flight path for the UAV 21301 within the target zone21512; and flying the UAV 21301 along the flight path.

UAV 21301 may follow the one or more terminal devices 102 and/or 500within the target zone 21512 to a coverage area 22622 of a furthernetwork access node 22620. Method 22800 may further include flying theUAV 21301 back to the network access node 22610 after escorting the oneor more terminal devices 102 and/or 500 to the coverage area 22622 ofthe further network access node 22620.

The one or more terminals 102 and/or 500 may travel along a predefinedroute, which may be based on a terrestrial transportation route overland and/or water. The predefined route may be based on an aviationtransportation route. The predefined route may be based on anastronautic transportation route.

The target zone 21512 may be based on a maximum communication range ofthe mobile access point 110. The target zone 21512 may be based on acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. The target zone 21512 may furtherinclude a target location 21510 based on a predefined threshold of acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. The communication quality parameter maybe based on a signal strength indicator and/or a signal qualityindicator. The one or more terminals 102 and/or 500 may change positionover time.

Method 22800 may further include flying the UAV 21301 along the flightpath with a ground speed based on one-half the difference of the firstvelocity and the second velocity. The first path 21701 may be at a firstaltitude and the second path 21702 may be at a second altitude. Theflight path may further include an ascent path 21603 to 21703 to thefirst altitude and a descent path 21704 to the second altitude. Thefirst path 21701 and/or the second path 21702 may have a greaterhorizontal distance than a vertical distance of the ascent path 21703and/or the descent path 21704. A charging station for the UAV 21301 maybe located along the flight path. Method 22800 may further includecommunicating with the one or more terminal devices 102 and/or 500 inthe target zone 21512. The functions of method 22800 may also beperformed by the means described above in relation to UAV 21301.

An unmanned aerial vehicle (UAV) may include: a mobile access point 110configured as a relay 22601 for a network access node 22610 and may beconfigured to communicate with one or more terminal devices 102 and/or500; the processor may be configured to: determine a target zone 21512based on the one or more terminal devices 102 and/or 500 and determine aflight path for the UAV within the target zone 21512; and an aviationsystem 21320 configured to fly the UAV along the flight path.

The UAV may follow the one or more terminal devices 102 and/or 500within the target zone 21512 to a coverage area 22622 of a furthernetwork access node 22620. Processor 21330 may be configured to controlthe aviation system 21320 to fly the UAV back to the network access node22610 after escorting the one or more terminal devices 102 and/or 500 tothe coverage area 22622 of the further network access node 22620.

The one or more terminals 102 and/or 500 may travel along a predefinedroute, which may be based on a terrestrial transportation route overland and/or water. The predefined route may be based on an aviationtransportation route. The predefined route may be based on anastronautic transportation route.

The target zone 21512 may be based on a maximum communication range ofthe mobile access point 110. The target zone 21512 may be based on acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. The target zone 21512 may furtherinclude a target location 21510 based on a predefined threshold of acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. The communication quality parameter maybe based on a signal strength indicator and/or a signal qualityindicator. The one or more terminals 102 and/or 500 may change positionover time.

Processor 21330 may be configured to control the aviation system 21320to fly the UAV along the flight path with a ground speed based onone-half the difference of the first velocity and the second velocity.The first path 21701 may be at a first altitude and the second path21702 may be at a second altitude. The flight path may further includean ascent path 21703 to the first altitude and a descent path 21704 tothe second altitude. The first path 21701 and/or the second path 21702may have a greater horizontal distance than a vertical distance of theascent path 21703 and/or the descent path 21704. A charging station forthe UAV may be located along the flight path.

A network access node 22610 may be configured to communicate with one ormore terminals 102 and/or 500, the network access node 22610 mayinclude: an unmanned aerial vehicle (UAV) 21301, the UAV 21301including: a mobile access point 110 configured as a relay 22601 for thenetwork access node 22610 and configured to communicate with the one ormore terminal devices 102 and/or 500; a processor 21330 configured to:determine a target zone 21512 based on the one or more terminal devices102 and/or 500 and determine a flight path for the UAV 21301 within thetarget zone 21512; and an aviation system 21320 configured to fly theUAV 21301 along the flight path; the network access node 22610including: a transceiver configured to communicate with the one or moreterminals 102 and/or 500; a network access node processor configured tohand over communication of the one or more terminal devices 102 and/or500 to the UAV 21301.

UAV 21301 may follow the one or more terminal devices 102 and/or 500within the target zone 21512 to a coverage area 22622 of a furthernetwork access node 22620. Processor 21330 may be configured to controlthe aviation system 21320 to fly the UAV 21301 back to the networkaccess node 22610 after escorting the one or more terminal devices 102and/or 500 to the coverage area 22622 of the further network access node22620.

The one or more terminals 102 and/or 500 may travel along a predefinedroute, which may be based on a terrestrial transportation route overland and/or water. The predefined route may be based on an aviationtransportation route. The predefined route may be based on anastronautic transportation route.

The target zone 21512 may be based on a maximum communication range ofthe mobile access point 110. The target zone 21512 may be based on acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. The target zone 21512 may furtherinclude a target location 21510 based on a predefined threshold of acommunication quality parameter for communications with the one or moreterminal devices 102 and/or 500. The communication quality parameter maybe based on a signal strength indicator and/or a signal qualityindicator. The one or more terminals 102 and/or 500 may change positionover time.

Processor 21330 may be configured to control the aviation system 21320to fly the UAV 21301 along the flight path with a ground speed based onone-half the difference of the first velocity and the second velocity.The first path 21701 may be at a first altitude and the second path21702 may be at a second altitude. The flight path may further includean ascent path 21703 to the first altitude and a descent path 21704 tothe second altitude. The first path 21701 and/or the second path 21702may have a greater horizontal distance than a vertical distance of theascent path 21703 and/or the descent path 21704. A charging station forthe UAV 21301 may be located along the flight path.

In an aspect of the disclosure, a network access node 110, networkaccess node 120, and a network access node 130 may be configured in atwo dimensional resource allocation as shown in FIG. 229 . In thisexample of FIG. 229 , the coverage areas may be distributed along ahorizontal plane. However, as shown in FIG. 230 , resource allocationmay be extended in a third dimension, e.g., altitude, with UAVs 21301that may include a mobile access point 110. Therefore, each UAV 21301may have a coverage zone 23010, 23020, 23030, 23040, 23050, 23060,23070, and 23080, respectively. A UAV 21301 may fly along a flight pathas described above within the coverage zone.

In addition, the designation for UAVs 21301 in a particular coveragezone may be dynamic. For example, UAV 21301 may be tracking a terminaldevice 102 in coverage zone 23080. The terminal device may travel intocoverage zone 23070 and the UAV 21301 from coverage zone 23070 with it.The UAV 21301 in coverage zone 23070, however, may not be communicatingwith any terminal devices. Accordingly, the UAV 21301 from coverage zone23080 may take over coverage zone 23070, while the UAV 21301 originallyin coverage zone 23070 may take over coverage zone 23080.

Thus, a coverage zone 23010-23080 may include a region defined by alength, a width, and an altitude. The coverage zone may include a UAV21301 with a mobile access point 110 for communication with one or moreterminal devices 102 and/or 500. The UAV 21301 may fly along a flightpath within a coverage zone 23010-23080.

In an aspect of the disclosure, FIG. 231 shows a UAV 23101. UAV 23101may be substantially similar to UAV 21301, and may include additionalfeatures. UAV 23101 may include flight control surfaces 21322. UAV 23101may include a rotatable structure 23110 including an airfoil 23120,e.g., one or more airfoils 23120. Although two airfoils 23120 are shownin FIG. 231 , UAV 23101 may have any number of airfoils 23120. Agenerator 23130 may be coupled with the rotatable structure 23110.Generator 23130 may be coupled to a battery 23140. Battery 23140 may bepart of power source 21340. Rotatable structure 23110 may be configuredto generate electricity that charges battery 23140 when air passing overairfoil 23120 causes rotatable structure 23110 and generator 23130 togenerate electricity.

Rather than (and/or in addition to) a UAV 21301 flying to a chargingand/or refueling station 22640 as discussed above, a UAV 23101 may beable to charge itself. As shown in FIG. 232 , UAV 23101 may determine aflight path including a descent 23204. UAV 23101 may then fly along thedescent 23204 at a velocity that air passing over the airfoil 23120turns rotatable structure 23110 and generator 23130 to generateelectricity, which may be stored in battery 23140. As an example, if UAV23101 is flying along a flight path described above including a firstpath 21701 at a first altitude and a second path 21702 at a secondaltitude, UAV 23101 may further extend its flight time by chargingbattery 23140 during descent path 21704.

Method 23300 of FIG. 233 is a method of charging an unmanned aerialvehicle (UAV). The UAV including a rotatable structure 23110 includingan airfoil 23120; a generator 23130 coupled with the rotatable structure23110; a battery 23140 coupled with the generator 23130, the rotatablestructure 23110 configured to generate electricity that charges thebattery 23140 when air passing over the airfoil 23120 causes therotatable structures 23110 and the generator 23130 to rotate, the method23300 including: determining a flight path for the UAV including adescent 23204; flying the UAV in the descent 23204 along the flight pathat a velocity that air passing over the airfoil 23120 turns therotatable structure 23110 and the generator 23130 to generateelectricity; and storing the electricity in the battery 23140. Thefunctions of method 23300 may also be performed by the means describedabove in relation to UAV 23101.

Additionally or alternatively, UAV 23101 may be fixed to a structure23410 in a wind as shown in FIG. 234 . Structure 23410 may be a fixedstructure or may be a cable-like structure. For example, UAV 23101 mayhave fixed-wing or autogyro flight control surfaces 21322 so that a wind23400 may keep UAV 23101 aloft, e.g., like a kite. Wind 23400 may alsogenerate electricity via rotatable structure 23110 and generator 23130.In another example, structure 23410 may be a fixed structure and may beable to support the weight of UAV 23101, so that it may be fixed inplace and wind 23400 passing over rotatable structure 22120 andgenerator 23130 may generate electricity to charge UAV 23101. In anotheraspect of the disclosure, UAV 21301 may be attached to structure 23410,which may include two cables so that UAV 21301 may be charged by thecables.

While attached to structure 23410, UAV 21301 and/or UAV 23101 may useits flight controls 21322 to drive towards positions that wouldinaccessible for a kite.

Once charged, UAV 23101 and/or UAV 21301 may detach from structure23410. Structure 23410 may be transferred to another UAV 21301 and/orUAV 23101, so that it does not fall to the ground.

Method 23500 of FIG. 235 is a method of charging an unmanned aerialvehicle (UAV). The UAV including a rotatable structure 23110 includingan airfoil 23120; a generator 23130 coupled with the rotatable structure23110; a battery 23140 coupled with the generator 23130, the rotatablestructure 23110 configured to generate electricity that charges thebattery 23140 when air passing over the airfoil 23120 causes therotatable structures 23110 and the generator 23130 to rotate, the method23500 including: fixing the UAV to a structure 23410 in a wind 23400with air passing over the airfoil 23120 that turns the rotatablestructure 23110 and the generator 23130 to generate electricity; andstoring the electricity in the battery 23140. The functions of method23500 may also be performed by the means described above in relation toUAV 23101.

Additionally or alternatively, as shown in FIG. 236 , a UAV 23101 may befixed to another UAV 23601, which may be a UAV 21301 or a UAV 23101, bya structure 23610. Structure 23610 may be flexible or rigid. Forexample, structure 23610, may be a chain-like structure or a cable.Structure 23610 may be a rod or bar. UAV 23601 may then transport UAV23101, e.g., towing or pushing, so that air causes rotatable structure23110 and generator 23130 to turn and generate electricity. UAV 23101may produce lift with its flight control surfaces 21322 or may passivelyfly, e.g., if UAV 23101 has fixed wings or has an autogyro rotor and isbeing transported by UAV 23601 or UAV 23101 is supported by UAV 23601.UAV 23601 and UAV 23101 may be in a flight formation and have energyconsumption requirements as discussed above.

Method 23700 of FIG. 236 237 is a method of charging an unmanned aerialvehicle (UAV). The UAV including a rotatable structure 23110 includingan airfoil 23120; a generator 23130 coupled with the rotatable structure23110; a battery 23140 coupled with the generator 23130, the rotatablestructure 23110 configured to generate electricity that charges thebattery 23140 when air passing over the airfoil 23120 causes therotatable structures 23110 and the generator 23130 to rotate, the method23500 including: fixing the UAV 23101 to a further UAV 23601;transporting the UAV 23101 with the further UAV 23601 with air passingover the airfoil 23120 that turns the rotatable structure 23110 and thegenerator 23130 to generate electricity; and storing the electricity inthe battery 23140. UAV 23101 may be coupled to further UAV 23601 via astructure 23610. The functions of method 23700 may also be performed bythe means described above in relation to UAV 23101.

Improved Service Recovery after Network Failure

There are various possible network scenarios where standardized terminaldevice behavior may cause lengthy delays in recovering voice or dataservices. As an example, the 3GPP LTE standard mandates certainprocedural behaviors that could cause long delays when a terminal devicetries to regain circuit-switched (CS), packet-switched (PS), or evolvedpacket-switched (EPS) services. While LTE is used an example in thefollowing description, the aspects described herein can also be appliedto other radio access technologies that involve the same or similarterminal device behavior.

One LTE scenario that could cause long service recovery times involvesNon-Access Stratum (NAS) signaling procedures. For example, when aterminal device in idle mode moves into a new Tracking Area (TA), the3GPP standard dictates that the terminal device should temporarilyattach to the network using a random access procedure and send aTracking Area Update (TAU) to the Mobility Management Entity (MME) ofthe new TA. However, in some scenarios there may be a network failure(e.g., radio access failure/disconnection or core network failure) thatprevents completion of the TAU. When this occurs, the 3GPP standardmandates that the NAS on the terminal device (e.g., the NAS softwarerunning as part of the protocol stack) should start a timer (e.g., timerT3411 with a duration of 10 s) and temporarily suspend further TAUattempts. As the terminal device is expected to wait until the timerexpires before attempting again, this can introduce long delays beforethe TAU can be completed. This same issue can also arise for other NASsignaling procedures, such as Location Area Updates (LAUs), Routing AreaUpdates (RAUs), Attach procedures, and Service Request procedures.Delays involved in Attach and Service Request procedures can beparticularly problematic, as a user of the terminal device may not beable to use the terminal device for data transfer until the NASsignaling procedure is completed.

This 3GPP-mandated behavior regarding the use of a timer beforeperforming another procedure attempt may also be sub-optimal inscenarios where fake cells are present. These fake cells areunauthorized equipment (e.g., set up by an unsanctioned or maliciousentity) that act like standard network access nodes by broadcastingsynchronization signals and system information and exchange other radioaccess signaling with terminal devices. However, as they areunauthorized, fake cells are not actually connected to the core networkand should be avoided due to their potentially malicious intent.

Accordingly, when a terminal device attempts to use a fake cell for theradio access connection to perform a core network signaling procedure(e.g., a NAS signaling procedure), the terminal device may detect anetwork failure due to the fake cell's inability to fully function as anetwork access node. If the fake cell causes a radio accessfailure/disconnection (e.g., does not respond to random access attemptsor releases the radio access connection), the terminal device mayinitiate a timer per the 3GPP standard and wait until the timer hasexpired before re-attempting the NAS signaling procedure. As the fakecell may still be unable to carry out the NAS signaling procedure, thesubsequent attempt will also fail, which will then prompt re-initiationof the timer. This procedure can continue until the terminal devicesreaches a threshold number of attempts (e.g., a maximum attempt countspecified by the 3GPP), after which the terminal device may be expectedto disable LTE for an extended duration timer (e.g., 3GPP timer T3402).If the fake cell causes a core network failure (e.g., by sending rejectmessages), the terminal device may block the TA that the fake cell isbroadcasting (thus preventing the terminal device from attempting theNAs signaling procedure on another network access node in this TA) ormay start an extended duration timer (e.g., 3GPP timers T3402, T3302, orT3212).

There can also be long service recovery times when a temporaryOut-of-Coverage (OOC) scenario causes the LTE system to reach athreshold number of registration attempts, which per the LTE standardtriggers initiation of an extended duration timer (e.g., 3GPP timerT3402). However, in some scenarios LTE service may become availablebefore the extended duration timer expires, and the terminal device maytherefore waste considerable time before attempting to establish LTEservice. For example, when a user carrying a terminal device enters anelevator or drives through a tunnel, there may be a temporary outage ofLTE service that causes the LTE system of the terminal device to reachthe threshold number of connection attempts. Even if the user exits theelevator or tunnel shortly thereafter, as per the 3GPP standard the LTEsystem may wait the full duration of the timer (e.g., 12 minutes in thecase of T3402) before attempting to establish LTE service.

These scenarios can be particularly problematic when a user attempts touse voice or data services while the LTE system is waiting for a timerto expire before completing a given core network signaling procedure.Accordingly, as recognized by this disclosure and described below,various aspects may provide specialized procedures that improve servicerecovery time and enable a terminal device to complete a core networksignaling procedure at an earlier time.

FIG. 238 shows an exemplary internal configuration of terminal device23800 according to some aspects. As shown in FIG. 238 , terminal device23800 may include antenna system 23802, RF transceiver 23804, andbaseband modem 23806. Antenna system 23802 and RF transceiver 23804 maybe configured in the manner of antenna system 202 and RF transceiver 204of terminal device 102 in FIG. 2 . Accordingly, in the receivedirection, antenna system 23802 may receive wireless radio signals andtransduce the wireless radio signals into analog radio signals. RFtransceiver 23804 may then perform radio processing on the analog radiosignals to obtain baseband data (e.g., IQ samples), which RF transceiver23804 may provide to baseband modem 23806 for baseband processing. Inthe transmit direction, baseband modem 23806 may provide baseband datato RF transceiver 23804, which may perform radio processing on thebaseband data to obtain analog radio signals. RF transceiver 23804 maythen provide the analog radio signals to antenna system 23802, which maythen wirelessly transmit the analog radio signals.

Baseband modem 23806 may be configured with the same or similarfunctionality described above for baseband modem 206 of terminal device102 in FIG. 2 . Accordingly, baseband modem 23806 may be configured toperform physical layer and protocol stack processing on baseband dataprovided by RF transceiver 23804 to recover user data (e.g., transportor application layer data) contained in the wireless radio signalsinitially received by antenna system 23802, and to perform protocolstack and physical layer processing on user data to obtain baseband data(e.g., IQ samples) for wireless transmission by RF transceiver 23804 andantenna system 23802.

As shown in FIG. 238 , baseband modem 23806 may include radio accessprocessor 23808 and core signaling controller 23812. In some aspects,radio access processor 23808 may be configured to handle the AccessStratum (AS) processing and signaling of baseband modem 23806, whichrefers to the processing and signaling involved in transmitting andreceiving data over the radio access network (e.g., to network accessnodes). Accordingly, in some aspects radio access processor 23808 may beconfigured to retrieve from a memory and execute program code thatdefines AS functionality as executable instructions. In some aspects,radio access processor 23808 may include digital signal processingcircuitry (e.g., hardware accelerators for physical layer processingtasks).

In some aspects, core signaling controller 23812 may be configured tohandle the non-Access Stratum (NAS) processing and signaling of basebandmodem 23806, which refers to the control signaling exchanged betweenterminal device 23800 and various core network nodes (e.g., MobilityManagement Entities (MME) in LTE, Mobile Switching Center (MSC) andServing GPRS Support Node (SGSN) in UMTS, and any other similar corenetwork node in another radio access technology). Accordingly, in someaspects, core signaling controller 23812 may be configured to retrievefrom a memory and execute program code that defines NAS functionality asexecutable instructions.

As introduced above, there may be several scenarios where servicerecovery time can be improved. FIG. 239 shows an exemplary firstscenario according to some aspects. As shown in FIG. 239 , terminaldevice 23800 may be located in the coverage area of network access nodes23902 and 23904 (e.g., may be within radio connection range of networkaccess nodes 23902 and 23904). In this scenario, network access nodes23902 and 23904 may belong to the same network tracking area 23900. Inan exemplary LTE context, network tracking area 23900 may be a TrackingArea (TA), which may be assigned a specific Tracking Area Code (TAC) bythe network operator.

FIG. 240 shows exemplary message sequence chart 24000, which illustratesexemplary operation of terminal device 23800 in the first scenarioaccording to some aspects. As shown in FIG. 240 , radio access processor23808 may first be camped on network access node 23902 in stage 24002.Core signaling controller 23812 may then trigger a core networksignaling procedure in stage 24004. For example, as radio accessprocessor 23808 may initially be in a radio idle mode (e.g., RRC Idle),and core signaling controller 23812 may trigger the core networksignaling procedure to perform a network tracking area update (e.g.,TAU, RAU, LAU), to perform a network attach procedure, or to establish avoice or data session. Exemplary core network signaling procedures cantherefore include TAUs, RAUs, LAUs, Attach procedures, and/or ServiceRequests.

The core network signaling procedure may therefore involve signalingexchange between core signaling controller 23812 and a core networknode, such as a Mobility Management Entity (MME), Serving GPRS SupportNode (SGSN), or Mobile Switching Center (MSC). As this signalingexchange may use the radio access network for wireless transport, coresignaling controller 23812 may request radio access connectionestablishment from radio access processor 23808 (e.g., an RRC ConnectionEstablishment Request) in stage 24006.

Radio access processor 23808 may therefore attempt to establish a radioaccess connection with network access node 23902 in stage 24008. Forexample, radio access processor 23808 may attempt a random accessprocedure with network access node 23902 as part of an attempt toestablish a radio access connection with which core signaling controller23812 can execute the core network signaling procedure. However, in thecase of FIG. 240 , the radio access connection establishment may fail.This can occur, for example, due to a random access failure.Accordingly, radio access processor 23808 may report the radio accessconnection establishment failure to core signaling controller 23812 instage 24010. Core signaling controller 23812 may therefore detect thatthe radio access connection establishment failed in stage 24012. Coresignaling controller 23812 may then update a failed cell list by addingnetwork access node 23902 (e.g., storing identity information of networkaccess node 23902 in a list that contains identity information ofnetwork access nodes that have failed). Core signaling controller 23812may also increment a connection attempt counter that tracks the numberof failed connection attempts (e.g., may increment the connectionattempt counter from 0 to 1). As further described below, core signalingcontroller 23812 may use the connection attempt counter to track failedradio access connection establishment attempts, and to stop furtherradio access connection establishment attempts when the connectionattempt counter reaches a threshold number of connection attempts.

Core signaling controller 23812 may also start a timer in stage 24016,where the timer may track the time since the last radio accessconnection establishment failure. In some aspects, the timer may be astandard-mandated timer. For example, in the case of LTE, the 3GPPstandard mandates that the NAS start timer T3411 when a random accessconnection establishment failure occurs as part of a NAS signalingprocedure. As specified by the 3GPP, the NAS is to temporarily suspendNAS signaling procedures on the failed cell until timer T3411 expires(e.g., 10 seconds).

However, instead of refraining from all core network signalingprocedures until the timer expires, terminal device 23800 may beginsearching for other network access nodes that could potentially be usedfor the core network signaling procedure. As shown in FIG. 240 , radioaccess processor 24014 may trigger a cell search in stage 24014 andbegin searching for any other network access nodes that are detectable.For example, radio access processor 23808 may be configured to instructcell searcher 23810 to perform a cell search. Cell searcher 23810, whichmay be a processor or digital hardware circuit configured to receive andprocess signals to detect pilot signals transmitted by network accessnodes, may then be configured to perform the cell search (e.g., byreceiving and processing baseband data provided by RF transceiver 23804to detect any pilot signals and identifying the corresponding networkaccess node that transmitted the pilot signal).

Cell searcher 23810 may then detect network access nodes and report thenetwork access nodes to radio access processor 23808. Radio accessprocessor 23808 may then evaluate the network access nodes to determinewhether they meet cell selection criteria (e.g., a set of thresholdsregarding radio measurement that define whether a network access nodecan be selected). In the example of FIG. 240 , radio access processor23808 may detect one or more available network access nodes, includingnetwork access node 23904. As previously indicated, network access node23904 may also be a part of network tracking area 23900. Radio accessprocessor 23808 may then report network access node 23904 as a detectednetwork access node to core signaling controller 23812 in stage 24018.

After receiving the indication that network access node 23904 has beendetected, core signaling controller 23812 may evaluate network accessnode 23904 based on a connection attempt counter and based on the failedcell list in stage 24020. For example, core signaling controller 23812may check the failed cell list to determine whether network access node23904 is in the failed cell list (e.g., where a radio access connectionestablishment procedure for the current core network signaling procedurehas already failed with network access node 23904). As network accessnode 23902 is the only network access node in the failed cell list, coresignaling controller 23812 may determine that network access node 23904is not in the failed cell list. Core signaling controller 23812 may alsocheck whether a connection attempt counter has reached a thresholdnumber of connection attempts. This threshold number of connectionattempts can be, for example, three, four, or five. As this is the firstconnection attempt (since the initial radio access connectionestablishment failure in stage 24008), core signaling controller 23812may determine that the connection attempt counter has not reached thethreshold number of connection attempts (e.g., may only be 1).

Accordingly, as network access node 23904 is not in the failed cell listand the connection attempt counter has not reached the threshold numberof connection attempts, core signaling controller 23812 may request forradio access processor 23808 to attempt another radio access connectionestablishment through network access node 23904. As the timer maysuspend radio access connection establishment attempts for networkaccess node 23902 (e.g., but not other network access nodes), radioaccess processor 23808 may be able to attempt another radio accessconnection establishment with network access node 23904 in stage 24024.In the exemplary scenario of FIG. 240 , this radio access connectionestablishment may be successful. Accordingly, network access node 23904may respond with a radio access connection setup in stage 24026, andradio access processor 23808 may send back a radio access connectionsetup complete in stage 24028.

Radio access processor 23808 may then inform core signaling controller23812 that the radio access connection establishment was successful instage 24030. As terminal device 23800 may now have an active radioaccess connection, core signaling controller 23812 may be able toperform the core network signaling procedure. Core signaling controller23812 may therefore reset the failed cell list (e.g., clear any networkaccess nodes from the failed cell list that failed during this corenetwork signaling procedure) in stage 24032 and perform the core networksignaling procedure with the core network through network access node23904 (e.g., using network access node 23904 for the radio accessconnection to interface with the core network) in stage 24034. Forexample, if the core network signaling procedure is a TAU, coresignaling controller 23812 may exchange NAS signaling with an MME of thecore network that indicates a new TA (e.g., that identifies networktracking area 23900). If the core network signaling procedure is anattach procedure or service request, core signaling controller 23812 mayexchange NAS signaling with the MME to complete the attach or tocomplete the service request. Various other core network signalingprocedures, for any radio access technology, are similarly applicable.

When a core network signaling procedure fails due to a radio accessfailure/disconnection with a first network access node, terminal device23800 may therefore keep its AS running at radio access processor 23808and continue searching for available network access nodes. Accordingly,if radio access processor 23808 detects an available second networkaccess node, terminal device 23800 may attempt to use the second networkaccess node to establish the radio access connection. Instead of waitingfor the timer to expire, terminal device 23800 may thus be able to usethe second network access node to establish a radio connection andsubsequently perform the core network signaling procedure. In somecases, this may enable terminal device 23800 to perform the core networksignaling procedure at an earlier time. This can be particularnoticeable to a user when they are attempting to use terminal device23800 for a voice or data session, as terminal device 23800 may be ableto complete the core network signaling procedure and initiate the voiceor data session sooner.

FIGS. 241A and 241B show exemplary message sequence chart 24100according to some aspects, which further describes the functionality ofterminal device 23800 in the first scenario (core network signalingprocedure failure due to radio access failure/disconnection). Aspreviously indicated regarding FIG. 240 , core signaling controller23812 may be configured to maintain a failed cell list (containingidentity information for network access nodes that have previouslyfailed for the current core network signaling procedure) and aconnection attempt counter (that counts the number of radio accessconnection establishment attempts for the current core network signalingprocedure). FIGS. 241A and 241B further illustrate the use of thisfailed cell list and connection attempt counter by core signalingcontroller 23812.

As shown in FIG. 241A, core signaling controller 23812 and radio accessprocessor 23808 may perform stages 24102-24124 in the same manner ofstages 24002-24024, respectively. Accordingly, after core signalingcontroller 23812 evaluates network access node 23902 in stage 24120 anddetermines that network access node 23902 is not in the failed cell listand that the connection attempt counter is less than the thresholdnumber of connection attempts, radio access processor 23808 may attempta radio access connection establishment with network access node 23904in stage 24124. However, in contrast to stage 24024, the radio accessconnection establishment attempt may fail in stage 24124. Radio accessprocessor 23808 may therefore notify core signaling controller 23812 ofthe radio access connection establishment failure in stage 24126. Afterdetecting the radio access connection establishment failure in stage24128, core signaling controller 23812 may in stage 24130 update thefailed cell list (e.g., add identity information for network access node23904 into the failed cell list that specifies that a radio accessconnection establishment attempt failed for network access node 23904during the current core network signaling procedure) and connectionattempt counter (e.g., increment from 1 to 2 due to the failed radioaccess connection establishment attempts for network access nodes 23902and 23904). Core signaling controller 23812 may also start the timer(e.g., restart the timer that was initiated in stage 24116, e.g. T3402).

Radio access processor 23808 may continue to search for availablenetwork access nodes with cell searcher 23810, and may accordinglydetect network access node 23906 (not explicitly shown in FIG. 239 ).Radio access processor 23808 may report network access node 23906 tocore signaling controller 23812 in stage 24132.

Core signaling controller 23812 may then evaluate network access node23906 with the connection attempt counter and the failed cell list instage 24134. For example, core signaling controller 23812 may comparethe connection attempt counter (e.g., its current value) to thethreshold number of connection attempts, and determine that theconnection attempt counter is less than the threshold number ofconnection attempts. Core signaling controller 23812 may also check thefailed cell list to determine whether network access node 23906 isincluded within the failed cell list, and may subsequently determinethat network access node 23906 is not included within the failed celllist.

Continuing to FIG. 241B (which shows the remainder of message sequencechart 24100), core signaling controller 23812 may then request radioaccess connection establishment with network access node 23906 fromradio access processor 23808. Radio access processor 23808 may thenattempt radio access connection establishment in stage 24136. However,as shown in FIG. 241B, the radio access connection establishment withnetwork access node 23906 may also fail. Radio access processor 23808may report the radio access connection establishment failure to coresignaling controller 23812 in stage 24138.

Core signaling controller 23812 may therefore detect the radio accessconnection establishment failure in stage 24140, and subsequently updatethe failed cell list (e.g., add network access node 23906 to the failedcell list) and update the connection attempt counter (e.g., incrementfrom 2 to 3) in stage 24142. Core signaling controller 23812 may alsorestart the timer in stage 24142.

In the example of message sequence chart 24100, the threshold number ofconnection attempts may be three. Accordingly, following the radioaccess connection establishment attempt failure for network access node23906, the connection attempt counter may reach the threshold number ofconnection attempts. Therefore, when radio access processor 23808reports another detected network access to core signaling controller23812 in stage 24144, core signaling controller 23812 may determine thatthe connection attempt counter has reached the threshold number ofconnection attempts when it evaluates the detected network access nodein stage 24146. Instead of request radio access connection establishmentfrom radio access processor 23808, core signaling controller 23812 maywait for the timer to expire before attempting another radio accessconnection establishment in stage 24148. For example, as radio accessconnection establishment has already failed the threshold number oftimes, this may mean that terminal device 23800 is in a low signalcoverage area. This in turn can indicate that subsequent radio accessconnection establishment attempts would also fail, and it may bepreferable to conserve battery power and wait until the timer expires(e.g., 10 s) before attempting another radio access connectionestablishment.

In a variation on the process of message sequence chart 24100, radioaccess processor 23808 may re-detect network access node 23902 in stage24132, and report network access node 23902 to core signaling controller23812 in stage 24132. Accordingly, when core signaling controller 23812compares the network access node 23902 with the failed cell list instage 24134, core signaling controller 23812 may determine that networkaccess node 23902 has already been involved in a failed radio accessconnection establishment attempt for the current core network signalingprocedure. Core signaling controller 23812 may therefore decide not torequest radio access connection establishment for network access node23902 from radio access processor 23808, and may instead wait untilradio access processor 23808 detects another cell or the timer expires.Core signaling controller 23812 may not increment the connection attemptcounter in this case (as no radio access connection establishmentattempt was actually made).

In some aspects, core signaling controller 23812 may be configured touse a failed cell list but no connection attempt counter (e.g., maycontinue to attempt radio access connection establishment on networkaccess nodes detected by radio access processor 23808 for an unlimitednumber of times). In other aspects, core signaling controller 23812 maybe configured to use a connection attempt counter but no failed celllist (e.g., may limit radio access connection establishment attempts tothe threshold number of attempts, but may allow repeated radio accessconnection establishment attempts on the same network access node).

In summary, when confronted with the first scenario where there is acore network signaling procedure failure due to radio access failure ordisconnection (e.g., random access failure or RRC connection release),terminal device 23800 may be configured to look for other availablenetwork access nodes and to attempt radio access connectionestablishment on these network access nodes before the timer expires.This can improve service recovery time, as terminal device 23800 may beable to complete the core network signaling procedure at an earliertime.

As previously introduced, there may also be scenarios where core networksignaling procedures fail due to core network failures. FIG. 242 showsan exemplary second scenario according to some aspects. As opposed tothe first scenario, this second scenario (core network signalingprocedure failure due to core network failure) may therefore involve afailure in the core network. With reference to FIG. 242 , terminaldevice 23800 may be located in the coverage area of network access nodes24204 and 24206. Network access nodes 24204 and 24206 may be located indifferent network tracking areas, where network access node 24204 ispart of network tracking area 24200 and network access node 24206 ispart of network tracking area 24202.

Using the 3GPP LTE standard as an example, an LTE terminal device mayreceive a NAS signaling rejection for certain core network signalingprocedures. For example, a terminal device may send a TAU to an MMEusing a first LTE cell (or, alternatively, for UMTS, the terminal devicemay send a RAU to an SGSN or a LAU to an MSC using a first UMTS cell).The terminal device may then receive a TAU Reject with a temporaryrejection cause, such as cause #17 (Network Failure). This temporarycore network failure can be, for example, due to the terminal device'sexisting subscription services (e.g., where lower priority users arerejected), network congestion, or network maintenance. As furtherdescribed below, the temporary core network failure can also be due to afake cell. Per the 3GPP standard, a terminal device that detects atemporary core network failure (e.g., by receiving a rejection thatspecifies a temporary cause from the core network in response to a corenetwork signaling procedure) is directed to start a timer (e.g., timerT3411) and to suspend further attempts at the core network signalingprocedure in the affected network tracking area until the timer expires.For example, as each network tracking area in LTE is served by aparticular MME, a terminal device following the 3GPP standard shouldsuspend attempts at core network signaling procedures with the MME thatis experiencing the temporary core network failure until the timerexpires. As long as the first LTE cell continues to have good signalstrength (e.g., satisfying the camping criteria), the terminal devicewill wait while camped on the first LTE cell, and then reattempt thecore network signaling procedure with the MME through the first LTEcell.

FIG. 243 shows exemplary message sequence chart 24300 according to someaspects, which shows functionality of terminal device 23800 for thesecond scenario. As shown in FIG. 243 , radio access processor 23808 mayfirst be camped on network access node 23902 in stage 24302. Coresignaling controller 23812 may then trigger a core network signalingprocedure in stage 24304, and may attempt the core network signalingprocedure in stage 24306. Although not explicitly shown in FIG. 243 ,stage 24306 can include the radio access connection establishmentattempt procedure of stages 24106-24108 in FIG. 241A. As opposed tomessage sequence charts 24000 and 24100, where there was a radio accessfailure, the radio access connection establishment in stage 24306 may besuccessful (e.g., radio access processor 23808 may successfully enterradio connected mode with network access node 23902).

However, the core signaling procedure in stage 24306 may fail due to acore network failure. For example, after core signaling controller 23812sends core network signaling to a core network node (e.g., to an MME),the core network node may respond by sending back core network signalingthat specifies a temporary core network failure (e.g., a TAU Reject withcause #17). In some radio access technologies, this core network failuremay impact the entire area that the core network node serves (e.g., theentire network tracking area, or the set of network access nodes servedby the core network node). For example, in the exemplary LTE case wherean MME serves all LTE cells in a given TA, a temporary core networkfailure may mean that core network signaling procedures through any LTEcell in the TA will fail.

Accordingly, while terminal device 23800 may not be able to immediatelycomplete the core network signaling procedure with a network access nodein network tracking area 24200 (and per the standard may have to waitfor the timer to expire before reattempting the core network signalingprocedure in network tracking area 24200), terminal device 23800 may beable to attempt and complete the core network signaling procedure with anetwork access node in another network tracking area. This couldtherefore allow terminal device 23800 to complete the core networksignaling procedure at an earlier time, and potentially allow the userto access voice or data services earlier.

As shown in FIG. 243 , core signaling controller 23812 may add networktracking area 24200 to a failed network tracking area list in stage24308. The failed network tracking area list may therefore identify thenetwork tracking areas (e.g., TAs) that have been involved in failedattempt for the current core network signaling procedure. Core signalingcontroller 23812 may also in stage 24308 start a timer that tracks thetime since the last temporary core network failure (e.g., 3GPP timerT3411). Depending on the standard, this timer may define the amount oftime that terminal device 23800 is expected to wait before re-attemptinga core network signaling procedure in the network tracking area.

As shown in FIG. 243 , radio access processor 23808 may trigger a cellsearch with cell searcher 23808 in stage 24310. Cell searcher 23808 maytherefore report detected network access nodes back to radio accessprocessor 23808, which may evaluate the detected network access nodesagainst a selection criteria (e.g., set of thresholds) to determinewhether any of the detected network access nodes are viable for radioaccess connection. In the example of FIG. 243 , cell searcher 23808 maydetect and report network access node 23904, which radio accessprocessor 23808 may determine meets the selection criteria. Radio accessprocessor 23808 may therefore report network access node 23904 to coresignaling controller 23812 in stage 24312. Radio access processor 23808may also determine the network tracking area of network access node23904, such as by receiving (via RF transceiver 23804) and processingsystem information broadcasted by network access node 23904 to identifya network tracking area specified in the system information

Core signaling controller 23812 may then evaluate network access node23904 with the failed network tracking area list. As previouslyindicated, a temporary core network failure may signify that corenetwork signaling procedures will fail if attempted on any networkaccess node in the affected network tracking area. Accordingly, coresignaling controller 23812 may check the failed network tracking arealist to determine whether the network tracking area of network accessnode 23904 is in the failed network tracking list. If, for example, acore network signaling procedure attempt had also failed while using anetwork access node in the same tracking area, core signaling controller23812 may determine that the network tracking area of network accessnode 23904 is listed in the failed network tracking area list. Coresignaling controller 23812 may therefore decide not to attempt the corenetwork signaling procedure through network access node 23904.

In the example of FIG. 242 , network access node 23904 may be intracking area 24202, which may not have been involved in a core networkfailure for the core network signaling procedure. Accordingly, astracking area 24202 is not in the network tracking area list, coresignaling controller 23812 may determine in stage 24314 that the corenetwork signaling procedure can be attempted through network access node23904. Core signaling controller 23812 may therefore attempt the corenetwork signaling procedure in stage 24316 (e.g., by establishing aradio access connection with network access node 23904 via radio accessprocessor 23808 and using the radio access connection to send signalingto the core network node as part of the core network signalingprocedure). This may occur before the timer (started in stage 24308)expires. For example, as the duration of the timer may only specify atime during which further core signaling procedure attempts aresuspended for the network tracking area involved in a core networkfailure, core signaling controller 23812 may be able to attempt coresignaling procedures through network access nodes in other networktracking areas.

As shown in FIG. 243 , the core network signaling procedure in stage24316 may be successful. As core signaling controller 23812 may haveperformed the core network signaling procedure before the timer expires,terminal device 23800 may be able to complete the core network signalingprocedure at an earlier time. After completing the core networksignaling procedure in stage 24316, core signaling controller 23812 mayreset the failed network tracking area list in stage 24318 (e.g., clearall entries).

In some aspects, core signaling controller 23812 may also use aprocedure attempt counter when operating in the second scenario. Thisprocedure attempt counter may function in a similar manner to theconnection attempt counter described above for message sequence charts24000 and 24100. Accordingly, core signaling controller 23812 mayincrement the procedure attempt counter each time that a core networksignaling procedure (e.g., on a network access node from a new networktracking area that is not in the failed network tracking area list)fails. When radio access processor 23808 reports detected network accessnodes (e.g., as in stage 24312), core signaling controller 23812 may beconfigured to determine whether the procedure attempt counter is lessthan the threshold number of connection attempts. If so (and if thenetwork tracking area of the detected network access node is not in thefailed network tracking area list), core signaling controller 23812 mayattempt the core network signaling procedure on the detected networkaccess node. If not, core signaling controller 23812 may not attempt thecore network signaling procedure, and may wait until the timer expiresbefore attempting the core network signaling procedure again.

In some aspects, the functionality of terminal device 23800 describedabove may also be advantageous in cases where fake cells are deployed.As previously introduced, these fake cells can be unauthorized equipmentthat is deployed by potentially malicious entities (e.g., to eavesdropor steal user information). These fake cells may be able to perform cellradio activity that may be largely indistinguishable from real cells.For example, fake cells may broadcast valid synchronization signals andbe able to exchange other radio access signaling with terminal devices.However, as they are unauthorized, fake cells may not interface with theoperators core network, and terminal devices may therefore not be ableto use fake cells to transmit or receive user data via the core network.Due to their potentially indistinguishable radio access behavior, aterminal device may not be able to detect whether it is connected to afake cell. This can be problematic, as the terminal device may get stuckon a fake cell.

FIG. 244 shows an example involving fake cells according to someaspects. In the example of FIG. 244 , terminal device 23800 mayinitially be camped on fake cell 24402. Terminal device 23800 may alsobe within the coverage area of network access node 24404. Network accessnode 24404 may be part of network tracking area 24400. Although fakecell 24402 is not actually part of the network, fake cell 24402 maybroadcast falsified system information that indicates that it is part ofnetwork tracking area 24400.

By using the functionality of message sequence charts 24000 and 24100described above for the first scenario, terminal device 23800 may beable to reduce the negative impacts of fake cell 24402. For example,core signaling controller 23812 may trigger a core network signalingprocedure (e.g., as in stages 24004 and 24104 of message sequence charts24000 and 24100). As terminal device 23800 is initially camped on fakecell 24402, radio access processor 23808 may then attempt radio accessconnection establishment with fake cell 24402.

As fake cell 24402 is not actually part of the network, terminal device23800 will not be able to complete the core network signaling procedurethrough fake cell 24402. Depending on its configured functionality, fakecell 24402 may be configured to handle the radio access connectionestablishment attempt by terminal device 23800 in various differentways. In a first case, fake cell 24402 may cause a radio access failurewhen radio access processor 23808 attempts radio access connectionestablishment. For example, fake cell 24402 may not respond to randomaccess attempts (e.g., RACH preambles transmitted by radio accessprocessor 23808), or may temporarily allow radio access processor 23808to establish a radio access connection (e.g., an RRC connection), butmay release (e.g., terminate) the radio access connection soon after itis established. This behavior by fake 24402 will cause a radio accessfailure.

Accordingly, terminal device 23800 may use the functionality for thefirst scenario (core network signaling procedure failure due to radioaccess failure) to resolve the issue caused by fake cell 24402. Inparticular, core signaling controller 23812 may detect the radio accessconnection establishment failure, and then initiate the functionalityfor the first scenario. Radio access processor 23808 may trigger a cellsearch to detect network access nodes. With reference to FIG. 244 ,terminal device 23800 may also be within the coverage area of networkaccess node 24404. Radio access processor 23808 may therefore detectnetwork access node 24404 with cell searcher 23810, and report networkaccess node 24404 to core signaling controller 23812. Following theprocedure of message sequence charts 24000 and 24100, core signalingcontroller 23812 may evaluate network access node 24404 with the failedcell list and connection attempt counter to determine whether a radioaccess connection establishment attempt should be made with networkaccess node 24404. As network access node 24404 is a valid cell, theradio access connection establishment attempt may be successful(alternatively, core signaling controller 23812 may continue with theprocess of message sequence chart 24100 starting at stage 24128). Coresignaling controller 23812 may therefore be able to complete the corenetwork signaling procedure via network access node 24404.

Accordingly, as core signaling controller 23812 can identify anothernetwork access node, core signaling controller 23812 may switch off offake cell 24402 and proceed with network access node 24404. Aspreviously indicated, core signaling controller 23812 may not be awarewhether fake cell 24402 is fake or valid. Terminal device 23800 maytherefore be able to use this functionality for the first scenarioirrespective of whether the initial network access node is fake orvalid.

The first case of fake cell behavior in the scenario of FIG. 244 maytherefore cause a radio access failure when terminal device 23800attempts the core network signaling procedure. In a second case of fakecell behavior, fake cell 24402 may send rejection messages withpermanent or temporary rejection causes. For example, fake cell 24402may allow radio access connection establishment, but may respond with arejection message when core signaling controller 23812 attempts the corenetwork signaling procedure. Using LTE as an example, after coresignaling controller 23812 sends NAS signaling, fake cell 24402 mayrespond with a registration/service rejection message a permanent cause,such as #3 “Illegal UE,” #6 “Illegal ME,” #7 “EPS services not allowed,”#8 “EPS services and non-EPS services not allowed, or an “Authenticationreject” (e.g., which can cause the terminal device to invalidate the SIMfor packet services and, for example, to start timer T3247 for aduration drawn randomly between 30-60 mins) Per the 3GPP standard, coresignaling controller 23812 may be expected to bar the network trackingarea of fake cell 24402 and trigger a search for other network trackingareas (e.g., first within the camped PLMN and subsequently on otherPLMNs, if applicable). However, as previously introduced, fake cell24402 may be able to broadcast falsified system information thatindicates that fake cell 24402 is part of network tracking area 24400.Accordingly, if following the LTE standard, core signaling controller23812 may bar all network access nodes in network tracking area 24400,and may therefore not attempt the core network signaling procedure onnetwork access node 24404 (even though it is a valid cell).

In another example of the second case of fake cell behavior using LTE,fake cell 24402 may respond with a registration/service rejectionmessage with a temporary cause, such as causes #95, #96 , #97 , #99, or#111 (e.g., with no integrity protection). Per the LTE standard,terminal device 23800 may be expected to set the counter to a maximumnumber of attempts, and start an extended duration timer (e.g., T3402,T3302, or T3312), which may lead to an absence of service for anextended duration of time. For example, T3402 and T3302 may default to12 minutes, while T3212 can be specified by the network (and cantherefore be set to a several hour duration by fake cell 24402).

In some cases, fake cells may also have advanced functionality thatenables them to change their broadcasted cell identifies (e.g.,potentially even in sync with a cell search procedure used by terminaldevices). For example, fake cell 24402 may be able to change its cellidentity, and may therefore be able to appear to a terminal device asdifferent cells at different times. In other cases, there may bemultiple fake cells that each use a different cell identity. These typesof fake cell activity, in particular when combined with the second caseof fake cell activity behavior involving core network failures, maycause issues for terminal devices.

Accordingly, in some aspects terminal device 23800 may be able tomitigate the negative impact by using a specialized fake cell mitigationprocedure. FIG. 245 shows exemplary message sequence chart 24500illustrating this specialized fake cell mitigation procedure accordingto some aspects. As shown in FIG. 245 , radio access processor 23808 mayinitially be camped on fake cell 24402 (which radio access processor23808 may not be able to differentiate from valid cells). Core signalingcontroller 23812 may then trigger a core network signaling procedure instage 24504. As radio access processor 23808 is camped on fake cell24402, radio access processor 23808 may establish a radio accessconnection with fake cell 24402. However, when core signaling controller23812 attempts to send core network signaling for the core networksignaling procedure through fake cell 24402, fake cell 24402 may cause acore network failure in stage 24506 by responding with a rejectionmessage that specifies a temporary cause with no integrity protection.For example, in the case of LTE, fake cell 24402 may respond with aregistration/service rejection message with a temporary cause, such ascauses #95, #96 , #97 , #99, or #111 (e.g., with no integrityprotection).

Core signaling controller 23812 may then in stage 24508 add fake cell24402 to a potential fake cell list and increment a procedure attemptcounter (e.g., from 0 to 1) that tracks the number of procedure attemptsfor the core network signaling procedure. Core signaling controller24508 may also start a timer in stage 24508 that tracks the amount oftime since a core network failure with a temporary cause. The timer canbe mandated by the standard (e.g., 3GPP timer T3411) as a duration oftime that a terminal device has to wait before re-attempting a corenetwork signaling procedure following a core network failure.

Core signaling controller 23812 may then request for radio accessprocessor 23808 to perform a cell search for all cells in stage 24510.More specifically, in some aspects core signaling controller 23812 mayrequest for radio access processor 23808 to detect all network accessnodes (that satisfy the selection criteria and are on the campednetwork, e.g., the camped PLMN) except those on potential fake celllist, and to randomly select one of the detected network access nodes toreport back to core signaling controller 23812. Core signalingcontroller 23812 may also request for radio access processor 23808 to,if no suitable network access nodes are detected (e.g., none thatsatisfy the selection criteria and are on the camped network), reportback the currently camped cell, e.g., fake cell 24402.

Radio access processor 23808 may then trigger the cell search at cellsearcher 23810 in stage 24512. Cell searcher 23810 may report back thenetwork access nodes identified during the search, and radio accessprocessor 23808 may determine whether any of the network access nodessatisfy the selection criteria, are on the camped network, and are noton the potential fake cell list. If there are any such network accessnodes, radio access processor 23808 may randomly select a network accessnode in stage 24514. If there are not, radio access processor 23808 mayselect the current network access node, e.g., fake cell 24402, in stage24514.

Radio access processor 23808 may then report the selected network accessnode to core signaling controller 23812 in stage 24516. Core signalingcontroller 23812 may then evaluate the selected network access node instage 24518 with the potential fake cell list and the procedure attemptcounter. For example, core signaling controller 23812 may determinewhether the selected network access node is on the potential fake celllist, and determine whether the procedure attempt counter is less thanthe threshold number of procedure attempts (e.g., 3, 4, or 5). In theexample of FIG. 245 , radio access processor 23808 may randomly selectnetwork access node 24404 to report to core signaling controller 23812as the selected network access node. Core signaling controller 23812 maytherefore determine that the selected network access node is not on thepotential fake cell list, and may also determine that the procedureattempt counter is less than the threshold number of procedure attempts.Core signaling controller 23812 may then attempt and successfullycomplete the core network signaling procedure with network access node24404 in stage 24520, e.g., before the timer expires. Core signalingcontroller 23812 may then reset the potential failed cell list in stage24522.

Instead of selecting a network access node that best satisfies aselection criteria (e.g., that has the highest signal strength) or thenetwork access node that is found first, radio access processor 23808may use a randomized selection procedure in stage 24514. Accordingly,even if fake cell 24402 is using an advanced cell identity switchingtechnique, or if there are multiple fake cells, radio access processor23808 may potentially avoid selecting a fake cell in stage 24514 byrandomizing the selection. Therefore, when fake cells are configuredwith the second case of fake cell behavior (e.g., causing core networkfailures for core network signaling procedures), terminal device 23800may have some robustness against fake cell behavior (as it may be ableto re-select off of fake cells and attempt the core network signalingprocedure on another network access node). This can also provide fasterservice recovery, as core signaling controller 23812 may successfullycomplete the core network signaling procedure in stage 24520 before thetimer expires.

In other scenarios, the connection attempt counter may have reached thethreshold number of connection attempts. Accordingly, core signalingcontroller 23812 may determine in stage 24518 that the core signalingprocedure should not be attempted immediately. Core signaling controller23812 may therefore wait until the timer expires and subsequentlyattempt the core network signaling procedure on the selected networkaccess node, e.g., network access node 24404.

In other scenarios, radio access processor 23808 may not be able todetect any other network access nodes that meet the selection criteria,are on the camped network, and are not on the potential fake cell list.Accordingly, radio access processor 23808 may report the current networkaccess node, e.g., fake cell 24402, back to core signaling controller23812 in stage 24516 as the selected network access node. Core signalingcontroller 23812 may therefore determine that the selected networkaccess node is on the potential fake cell list in stage 24518, andconsequently that the core network signaling procedure should not beattempted immediately. Core signaling controller 23812 may thereforewait until the timer expires and subsequently attempt the core networksignaling procedure on the selected network access node, e.g., fake cell24402. As the core network signaling procedure will be re-attempted on afake cell, it will presumable fail again. However, as the duration ofthe timer has now passed, radio access processor 23808 may be able todetect more network access nodes and may therefore be able to randomlyselect another network access node (other than fake cell 24402). Coresignaling controller 23812 may then be able to successfully complete thecore network signaling procedure with this selected network access node.

FIG. 246 shows another example according to some aspects. Althoughsimilar to the case of FIG. 246 , fake cell 24402 may cause a corenetwork failure by rejecting the core network signaling procedure with apermanent cause (e.g., permanent cause without integrity protection).Terminal device 23800 may therefore follow a different procedure, inparticular when the applicable standard (e.g., LTE) specifies adifferent procedure for core network failures with permanent causes.

As shown in FIG. 246 , radio access processor 24602 may likewise begincamped on fake cell 24502 in stage 24602. Core signaling controller23812 may then trigger a core network signaling procedure through fakecell 24402 in stage 24604. Fake cell 24402 may cause a core networkfailure by rejecting the core network signaling procedure with apermanent cause in stage 24606. For example, in the case of LTE, fakecell 24402 may respond with a registration/service rejection messagespecifying a permanent cause, such as #3 “Illegal UE,” #6 “Illegal ME,”#7 “EPS services not allowed,” #8 “EPS services and non-EPS services notallowed,” or an “Authentication reject” Per the 3GPP standard, coresignaling controller 23812 may be expected to bar the entire networktracking area of fake cell 24402 (e.g., network tracking area 24400,which also includes network access node 24404), and/or to invalidate theSIM for packet services.

However, core signaling controller 23812 and radio access processor23808 may then execute the same or similar procedure in stages24608-24616 as specified above for stages 24508-24514. Accordingly, coresignaling controller 23812 may add fake cell 24402 to the potential fakecell list, increment the procedure attempt counter, and start the timerin stage 24608. Core signaling controller 23812 may then request a cellsearch from radio access processor 23808 in stage 24610. Radio accessprocessor 23808 may then perform a cell search with cell searcher 23810in stage 24612. If radio access processor 23808 detects network accessnodes that satisfy the selection criteria, are on the camped network,and are not on the potential fake cell list, radio access processor23808 may randomly select a network access node in stage 24614. If radioaccess processor 23808 does not detect any such network access nodes,radio access processor may select the current network access node, e.g.,fake cell 24402, in stage 24614.

Radio access processor 23808 may then report the selected network accessnode to core signaling controller 23812 in stage 24616. Core signalingcontroller 23812 may then evaluate the selected network access node withthe potential fake cell list and the procedure attempt counter in stage24518. In the example of FIG. 246 , radio access processor 23808 mayselect network access node 24404 as the selected network access node.Core signaling controller 23812 may thus determine that network accessnode 24404 is not on the potential fake cell list and that the procedureattempt counter is less than the threshold number of connectionattempts. Core signaling controller 23812 may then attempt andsuccessfully complete the core network signaling procedure throughnetwork access node 24404 in stage 24620, and may reset the potentialfake cell list in stage 24622.

In other scenarios, core signaling controller 23812 may determine thatthe procedure attempt counter has reached the threshold number ofprocedure attempts in stage 24618. In some aspects, core signalingcontroller 23812 may then consider the SIM of terminal device 23800invalid (e.g., as specified per 3GPP handling for CS/PS and CS&PSservices; for example, where terminal device 23800 may start a timer(e.g., T3245, with random duration drawn between 12-48 hours) and, onexpiry, consider the SIM as valid again for CS/PS services). In otherscenarios, radio access processor 23808 may not be able to detect anyother network access nodes in stage 24614 that satisfy the selectioncriteria, are on the camped network, and are not on the potential fakecell list. Radio access processor 23808 may therefore report the currentnetwork access node, e.g., fake cell 24402, as the selected networkaccess node in stage 24616. Core signaling controller 23812 may thenproceed according to the standard, such as by barring the networktracking area of fake cell 24402. Accordingly, similarly to the case ofmessage sequence chart 24500, terminal device 23800 may be able tocomplete the core signaling procedure before the timer expires, and maytherefore in some cases mitigate the negative impacts of fake cells.

In some aspects, the functionality of terminal device 23800 described inFIG. 243 for in the second scenario (core network signaling procedurefailure due to core network failure) may also be advantageous when fakecells are present. FIG. 247 shows an example similar to FIG. 242 whereone of the network access nodes is replaced by a fake cell. As shown inFIG. 247 , terminal device 23800 may be located within the coverageareas of fake cell 24704 and network access node 24706. Fake cell 24704may be broadcasting falsified system information that indicates that itis part of network tracking area 24700. Network access node 24706 may bea part of tracking area 24702.

In the example of FIG. 247 , radio access processor 23808 may initiallybe camped on fake cell 24704 (but may not be aware that fake cell 24704is a fake cell). Core signaling controller 23812 may then trigger a corenetwork signaling procedure. However, fake cell 24704 may cause a corenetwork failure (e.g., by responding with a rejection message with apermanent or temporary cause). Terminal device 23800 may then follow thefunctionality for the second scenario described in message sequencechart 24300. Accordingly, core signaling controller 23812 may addnetwork tracking area 24700 to the failed network tracking area list andstart the timer (for counting down until a subsequent attempt of a corenetwork signaling procedure can be made). After radio access processor23808 detects and reports network access node 24706, core signalingcontroller 23812 may determine that network access node 24706 is part ofnetwork tracking area 24702, which is not in the failed network trackingarea list. Core signaling controller 23812 may then attempt the corenetwork signaling procedure with network access node 24706 (e.g., beforethe timer expires). As network access node 24706 is a valid cell, thecore network signaling procedure may be successful. Core signalingcontroller 23812 may therefore be able to complete the core networksignaling procedure at an earlier time.

This functionality of terminal device 23800 may therefore improveperformance in the first and/or second scenarios, as well as when thereare fake cells present. This can enable terminal device 23800 tocomplete core network signaling procedures at an earlier time, and thusenable a user to access voice or data services at an earlier time.

Various aspects of this disclosure can also provide improved servicerecovery for multi-mode terminal devices after network failure. Forexample, many terminal devices support multiple radio accesstechnologies and therefore be multi-mode terminal devices. A commonexample is a multi-mode terminal device that supports LTE as well asUMTS and GSM. As LTE offers higher data rates and overall betterperformance, LTE may be considered the primary radio access technology(e.g., preferred over UMTS and GSM) while UMTS and GSM may be legacyradio access technologies.

As previously described, a terminal device using LTE may be expected tofollow the 3GPP standard. However, as recognized by this disclosure,some procedures defined in the 3GPP standard may be sub-optimal incertain scenarios. One such scenario is when a multi-mode terminaldevice attempting registration on an LTE cell experiences a randomaccess failure, such as due to weak LTE coverage. The 3GPP standarddictates that, in this scenario, “If the attach attempt counter is equalto 5, then the UE shall delete any LAI, TMSI, ciphering key sequencenumber and list of equivalent PLMNs and set the update status to U2 NOTUPDATED. A UE operating in CS/PS mode 1 of operation shall select GERANor UTRAN radio access technology and proceed with appropriate MM or GMMspecific procedures. NOTE: The UE supporting A/Gb mode or lu mode candisable the E-UTRA capability as specified in sub-clause 4.5” (3GPP TS24.301, Section 5.5.1.3.6, “Abnormal cases in the UE”). Accordingly,once the terminal device has attempted to attach to an LTE cell fivetimes (e.g., when the attach attempt counter reaches five), the terminaldevice should temporarily suspend LTE attach attempts and switch to alegacy radio access technology (e.g., UMTS or GSM).

However, 3GPP standard specifies that, should this happen, LTE attachattempts should be suspended for a general default value of 12 minutes(e.g., the default 12 min duration of timer T3402). This is an extendedduration of time during which the higher performance LTE service willnot be available to a user. Accordingly, the user may only be able touse legacy radio access technologies during this time, which have slowerdata rates and generally lower performance. The terminal device maytherefore become ‘stuck’ on the legacy radio access technologies, andfurther attempts to attach to LTE will be suspended until the timerexpires (e.g., until timer T3402 expires) even if LTE service actuallybecomes available at an earlier time.

The following use cases describe this issue in further detail. In afirst use case, a terminal device may camp on an LTE cell but may be ina weak LTE coverage area (e.g., as the terminal device is in anelevator, tunnel, parking garage, or other field location with weakcoverage). When the terminal device attempts LTE registration (e.g., toobtain an active connection, such as for voice or data services), therandom access procedure will fail and will continue to fail up to thethreshold number of registration attempts (e.g., the maximum attemptcount). Per the 3GPP standard, the terminal device may disable LTE forthe specified timer duration (e.g., 12 minutes), and may switch to thelegacy UMTS/GSM radio access technologies to try to register. Theterminal device may eventually be able to camp on and register with alegacy UMTS/GSM network (e.g., after the terminal device exits the weakcoverage area). However, even though the terminal device may re-enter astrong LTE coverage area, the terminal device may continue to wait untilthe timer expires before reattempting LTE registration. The terminaldevice will therefore become stuck on the legacy network and the userwill not be able to utilize the higher performance capabilities of LTE.

In a second use case, a terminal device may initially camp on an LTEcell but may be in a weak coverage area, such as in a first networktracking area of the LTE network. The terminal device may continuallyattempt LTE registration, but the registration attempts may fail and theterminal device may reach the threshold number of registration attempts.The terminal device may then, per the 3GPP standard, disable LTE for thetimer duration and revert to the legacy UMTS/GSM radio accesstechnologies. After camping and establishing a connection with thelegacy UMTS/GSM network, the terminal device may continue to wait untilthe timer expires before reattempting LTE registration. Accordingly,even when the terminal device moves into a second network tracking areaof the LTE network that has strong LTE coverage, the terminal devicewill remain stuck on the legacy UMTS/GSM network until the timerexpires.

Accordingly, various aspects of this disclosure present an improvedapproach that can help a multi-mode terminal device regain service for aprimary radio access technology at an earlier time (e.g., instead ofwaiting for the timer to expire without reattempting registrationbeforehand). While some examples described herein may refer to LTE,these aspects can be applied for any primary radio access technology(e.g., a preferred or highest performance radio access technologysupported by a multi-mode terminal device) of a multi-mode terminaldevice.

FIG. 248 shows an exemplary internal configuration of terminal device24800 according to some aspects. As shown in FIG. 248 , terminal device24800 may include antenna system 24802, RF transceiver 24804, andbaseband modem 24806. Antenna system 23802 and RF transceiver 23804 maybe configured in the manner of antenna system 202 and RF transceiver 204of terminal device 102 in FIG. 2 . Accordingly, in the receivedirection, antenna system 24802 may receive wireless radio signals andtransduce the wireless radio signals into analog radio signals. RFtransceiver 24804 may then perform radio processing on the analog radiosignals to obtain baseband data (e.g., IQ samples), which RF transceiver24804 may provide to baseband modem 24806 for baseband processing. Inthe transmit direction, baseband modem 24806 may provide baseband datato RF transceiver 24804, which may perform radio processing on thebaseband data to obtain analog radio signals. RF transceiver 24804 maythen provide the analog radio signals to antenna system 24802, which maythen wirelessly transmit the analog radio signals.

Baseband modem 24806 may be configured with the same or similarfunctionality described above for baseband modem 206 of terminal device102 in FIG. 2 . Accordingly, baseband modem 24806 may be configured toperform physical layer and protocol stack processing on baseband dataprovided by RF transceiver 24804 to recover user data (e.g., transportor application layer data) contained in the wireless radio signalsinitially received by antenna system 24802, and to perform protocolstack and physical layer processing on user data to obtain baseband data(e.g., IQ samples) for wireless transmission by RF transceiver 24804 andantenna system 24802.

Terminal device 24800 may be a multi-mode terminal device, and maytherefore support a plurality of radio access technologies. As shown inFIG. 248 , baseband modem 24806 may include primary radio accessprocessor 24808 (including cell searcher 24810), primary core signalingcontroller 24812, legacy radio access processor 24814, and legacy coresignaling controller 24816. Primary radio access processor 24808 andprimary core signaling controller 24812 may therefore be responsible forthe baseband functionality (e.g., physical layer and protocol stackprocessing) of a primary radio access technology of terminal device24800 (e.g., LTE). Legacy radio access processor 24814 and legacy coresignaling controller 24816 may be responsible for the basebandfunctionality (e.g., physical layer and protocol stack processing) of alegacy radio access technology of terminal device 24800 (e.g., UMTS orGSM). In some aspects, baseband modem 24806 may include one or moreadditional legacy radio access processors and legacy core signalingcontrollers to support the baseband functionality of one or moreadditional legacy radio access technologies. The term primary radioaccess technology system therefore refers to the combination of primaryradio access processor 24808 and primary core signaling controller24812, while the term legacy radio access technology system refers tothe combination of legacy radio access processor 24814 and legacy coresignaling controller 24816.

Similar to as described above for radio access processor 23808 in FIG.238 , primary radio access processor 24808 and legacy radio accessprocessor 24814 may be configured to handle AS processing and signalingfor their respective radio access technologies. Similar to as describedabove for core signaling controller 23812, primary core signalingcontroller 24812 and legacy core signaling controller 24816 may beconfigured to handle NAS processing and signaling for their respectiveradio access technologies. While FIG. 248 shows antenna system 24802 asa single component, in some aspects antenna system 24802 may include oneor more antennas for the primary radio access technology system to useand one or more antennas for the legacy radio access technology to use.Additionally or alternatively, while FIG. 248 shows RF transceiver 24804as a single component, in some aspects radio transceiver 24804 mayinclude a first RF transceiver for the primary radio access technologysystem to use and a second RF transceiver for the legacy radio accesstechnology to use.

As previously introduced, in some aspects terminal device 24800 may beconfigured to use an improved approach to recover service for a primaryradio access technology following a radio access failure. FIGS. 249 and250A-250B illustrate examples of this functionality according to someaspects. Starting with FIG. 249 , the primary radio access technologysystem (including primary radio access processor 24808 and primary coresignaling controller 24812) may begin by camping on a network accessnode of the primary network in stage 24902. This can be done by primaryradio access processor 24808, which as previously indicated may beconfigured to handle AS processing and signaling (which includes radioaccess connections). Then, the primary radio access technology systemmay trigger a registration attempt (e.g., to eventually perform a corenetwork signaling procedure, such as a TAU or a service request for avoice or data session) in stage 24904. Accordingly, primary coresignaling controller 24812 may perform a first registration attempt instage 24904. However, in the example of FIG. 249 , terminal device 24800may initially be in a weak coverage area of the primary network (e.g.,in an elevator, in a tunnel, in a parking garage or other area with weakcoverage), and the registration attempt may fail due to a radio accessfailure. For example, when radio access processor 24808 attempts arandom access procedure, the random access procedure may fail. This willin turn cause the registration procedure by primary core signalingcontroller 24812 to fail.

Primary core signaling controller 24812 may continue to performregistration attempts in stages 24906-24912, which may each also fail.Primary core signaling controller 24812 may keep a registration attemptcounter that increments for each registration attempt. If the thresholdnumber of registration attempts is, for example, five, primary coresignaling controller 24812 may determine in stage 24914 that thethreshold number of registration attempts has been reached.

In the example of FIG. 249 , terminal device 24800 may be following astandard (e.g., the LTE standard) that dictates that the primary radioaccess technology should be disabled for the duration of a timer (e.g.,T3402 with a default duration of 12 minutes) before any furtherregistration attempts are made. Accordingly, as shown in FIG. 249 ,primary core signaling controller 24812 may start the timer in stage24916. Primary core signaling controller 24812 may also updated a failednetwork tracking area list in stage 24914, such as by adding the networktracking area of the camped network access node of the primary network(to which the registration attempts in stages 24904-24912 were made) tothe failed network tracking area list. The failed network tracking arealist may therefore identify the network tracking areas on whichregistration attempts have failed.

Primary core signaling controller 24812 may then disable radio activitythe primary radio access technology system. For example, primary coresignaling controller 24812 may disable primary radio access processor24808, which may therefore suspend further radio activity by the primaryradio access technology system until further notice. This can includedisabling frequency scans and cell searches.

As registration with the primary radio access technology has failed, thelegacy radio access technology system (including legacy radio accessprocessor 24814 and legacy core signaling controller 24816) may camp ona network access node the legacy network (e.g., UMTS or GSM) in stage24918. This can be performed by legacy radio access processor 24814. Thelegacy radio access technology system may then attempt and successfullyperform registration in stage 24920.

In some cases, it may take the legacy radio access technology system aduration of time to successfully complete registration in stage 24920.For example, if terminal device 24800 is initially in a weak coveragearea, such as an elevator, legacy radio access processor 24814 may notbe able to immediately complete a random access procedure with thelegacy network. Accordingly, it may take several attempts and/or aduration of time for legacy core signaling controller 24816 to completeregistration on the legacy network.

However, the fact that legacy core signaling controller 24816 hassuccessfully registered may indicate that coverage conditions have alsoimproved for the primary network. Accordingly, as shown in FIG. 249 ,primary core signaling controller 24812 may detect that the legacy radioaccess technology system has registered on the legacy network, and mayre-enable the primary radio access technology system (e.g., re-enableits radio activity). Primary core signaling controller 24812 maytherefore re-enable the primary radio access technology system beforethe timer expires. As radio activity for the primary radio accesstechnology system is re-enabled, primary radio access processor 24808may trigger a cell search with cell searcher 24810. Cell searcher 24810may then detect network access nodes in stage 24924 and report thenetwork access nodes to primary radio access processor 24808. Primaryradio access processor 24808 may identify a network access node thatsatisfies the selection criteria and report the network access node toprimary core signaling controller 24812.

Primary core signaling controller 24812 may then evaluate the networkaccess node with the failed network tracking area list in stage 24926.For example, primary core signaling controller 24812 may determinewhether the network tracking area of the network access node is on thefailed network tracking area list. In the example of FIG. 249 , thenetwork tracking area of the network access node is not on the failednetwork tracking area list. Primary core signaling controller 24812 maytherefore attempt registration again in stage 24928, which include arandom access attempt by primary radio access processor 24808. This canoccur before the timer (started in stage 24916) expires. As shown inFIG. 249 , the random access attempt and registration attempt may besuccessful.

The primary radio access technology system therefore may complete theregistration before the timer expires. Accordingly, compared to thestandard case where a terminal device waits until the timer expiresbefore attempting any further registrations on the primary network,terminal device 24800 may be able to complete registration at an earliertime. Terminal device 24800 may therefore use successful registration bythe legacy radio access technology system as a triggering condition toattempt another registration on the primary network (e.g., assuming sucha registration has not already been attempted in the same networktracking area). This can be particularly beneficial in cases whereterminal device 24800 is in a weak coverage area such as an elevator,tunnel, or parking garage, as successful registration on the legacynetwork may indicate that registration can also be complete on theprimary network (as the temporarily weak coverage conditions have likelypassed).

In a variation of the example of FIG. 249 , the registration attempt onthe primary network with the network access node in stage 24928 may alsofail. In some cases, primary core signaling controller 24812 may thenadd the network tracking area of the network access node to the failednetwork tracking area list, re-start the timer, and disable the primaryradio access technology system (e.g., disable its radio activity). Then,when the legacy radio access technology system eventually registers onthe legacy network, the primary radio access technology system may againtry to identify a network access node that satisfies the selectioncriteria and is in a network tracking area that is not on the failednetwork tracking area list. The primary radio access technology systemmay then attempt the registration procedure using this network accessnode.

In some aspects, terminal device 24800 may be configured to only performone registration attempt on the primary network while the timer isrunning. FIGS. 250A and 250B show exemplary message sequence chart25000, which illustrate this procedure according to some aspects. Asshown in FIG. 250A, the primary radio access technology system and thelegacy radio access technology system may perform stages 25002-25014 inthe same manner as stages 24902-24914 in FIG. 249 . However, as terminaldevice 24800 may be configured to perform only one registration attempton the primary network when the timer is running, primary core signalingcontroller 24812 may not use a failed network tracking area list.Accordingly, in stage 25016 primary core signaling controller 24812 maystart the timer and disable the primary radio access technology system(but not update or use a failed network tracking area list). The primaryradio access technology system and legacy radio access technology systemmay then perform stages 25018-25024 in the manner of stages 24918-24924of FIG. 249 .

After primary radio access processor 24808 reports a network access nodein the primary network to primary core signaling controller 24812 instage 25024, primary signaling controller 24812 may perform aregistration attempt through the network access node in stage 25026(e.g., before the timer expires, and without evaluating the networkaccess node with a failed network tracking area list). In some cases,the registration attempt may succeed, and the primary radio accesstechnology system may therefore complete registration on the primarynetwork. In the example of FIGS. 250A and 250B, the registration attemptin stage 25026 may fail, and subsequent registration attempts up tostage 25028 may also fail. Primary core signaling controller 24812 maytherefore determine that the threshold number of registration attemptshas been reached in stage 25030.

Primary core signaling controller 24812 may therefore start the timerand disable the primary radio access technology system in stage 25032.The legacy radio access network system may camp on and successfullyregister with the legacy network in stages 25034 and 25036. As primarycore signaling controller 24812 may be configured to only use onesubsequent registration attempt following an initial failure (e.g., thatis triggered by a successful registration by the legacy radio accesstechnology system on the legacy network), primary core signalingcontroller 24812 may keep the primary radio access technology systemdisabled until the timer expires in stage 25038. Primary core signalingcontroller 24812 may re-attempt registration after this occurs.

Accordingly, this functionality may enable terminal device 24800 tore-establish service for a primary radio access technology (e.g., LTE)at an earlier time (e.g., before the timer expires). As described above,primary core signaling controller 24812 may use successful registrationby the legacy radio access technology as a trigger for re-attemptingregistration on the primary network. This can be particularly usefulwhen terminal device 24800 is temporarily in a weak coverage area (e.g.,an elevator, tunnel, parking garage or the like), as a successfulregistration by the legacy radio access technology can indicate that asuccessful registration is also possible for the primary radio accesstechnology.

FIG. 251 shows exemplary flow chart 25100 further illustrating thisfunctionality of terminal device 24800 according to some aspects. Asshown in FIG. 251 , primary core signaling controller 24812 may firstattempt to register on the primary network in stage 25102. If the radioaccess connection by primary radio access processor 24808 is successfulin stage 25104, primary core signaling controller 24812 may complete theregistration and register with the primary network in stage 25106. Ifthe radio access connection fails in stage 25104 (e.g., a failure of therandom access procedure by primary radio access processor 24808),primary core signaling controller 24812 may determine whether thethreshold number of registration attempts has been reached. If not,primary core signaling controller 24812 may increment the registrationattempt counter and return to stage 25102 to re-attempt registration onthe primary network. If the threshold number of registration attemptshas been reached, primary core signaling controller 24812 may disablethe primary radio access technology system and start the timer in stage25110. Legacy core signaling controller 24816 may then attempt toregister on the legacy network in stage 25110. If registration on thelegacy network is not successful, legacy core signaling controller 24816may re-attempt to register on the legacy network in stage 25114, and mayfollow any other applicable standardized procedures for legacy networkregistration failure.

If the registration on the legacy network is a success, primary coresignaling controller 24812 may detect the successful registration on thelegacy network in stage 25116. Primary core signaling controller 24812may use this as a triggering condition to enable the primary radioaccess technology system and attempt to register on the primary networkagain in stage 25118. If the registration on the primary network issuccessful (e.g., there is no radio access failure, such as a randomaccess procedure failure), primary core signaling controller 24812 mayregister with the primary network in stage 25122.

Conversely, if the registration on the primary network is not successful(e.g., due to a random access procedure, radio access connection release(e.g., RRC release), or other radio access failure), primary coresignaling controller 24812 may add the network tracking area of thenetwork access node (through which registration in stage 25120 wasattempted) to the failed network tracking area list in stage 25124.Primary core signaling controller 24812 may keep the primary radioaccess technology enabled in stage 25126 while legacy core signalingcontroller 24816 may camp and register on the legacy network.

Primary core signaling controller 24812 may continue attempting to campand register on network access nodes of the primary network that are innetwork tracking areas that are not in the failed network tracking areain stage 25128. For example, radio access processor 24808 may detect anetwork access node in the primary network that satisfies the selectioncriteria, and may report the network access node to primary coresignaling controller 24812. Primary core signaling controller 24812 maydetermine whether the network access node is in the failed networktracking area list. If not, primary core signaling controller 24812 mayattempt to register on the primary network through the network accessnode. If so, or if primary radio access processor 24808 does not detectany network access nodes that satisfy the selection criteria, primarycore signaling controller 24812 may wait until the timer expires tore-attempt registration on the primary network.

FIG. 252 shows an exemplary network scenario according to some aspectswhere this functionality may enable terminal device 24800 tore-establish service for its primary radio access technology at anearlier time. As shown in FIG. 252 , terminal device 24800 may start outin a weak coverage area at time 25202. Accordingly, the primary radioaccess technology system may not be able to register on the primarynetwork, and may suspend further attempts and start a timer at time25204.

Terminal device 24800 may eventually move into stronger coverage at time25206, at which point the legacy radio access technology system maysuccessfully register on the legacy network. The primary radio accesstechnology system may detect this successful registration, and maytrigger a registration attempt on the primary network (before the timeexpires). The registration may be successful, and terminal device 24800may become registered on the primary network at time 25208.

FIG. 253 shows exemplary method 25300 of operating a communicationdevice according to some aspects. As shown in FIG. 253 , method 25300includes attempting to initiate a first core network signaling procedurethrough a first network access node (25302), detecting a radio accessfailure or disconnection for the first core network signaling procedure(25304), starting a timer for a second core network signaling procedure(25306), detecting a second network access node (25308), and attemptingto initiate the second core network signaling procedure through thesecond network access node before the timer expires in response todetecting the second network access node (25310).

FIG. 254 shows exemplary method 25400 of operating a communicationdevice according to some aspects. As shown in FIG. 254 , method 25400includes attempting to initiate a first core network signaling procedurethrough a first network access node (25402), detecting a core networkfailure for the first core network signaling procedure (25404),detecting a second network access node (25406), determining whether thesecond network access node is in a same network tracking area as thefirst network access node (25408), and attempting to initiate a secondcore network signaling procedure through the second network access nodein response to determining that the second network access node is not inthe same network tracking area (25410).

FIG. 255 shows exemplary method 25500 of operating a communicationdevice according to some aspects. As shown in FIG. 255 , method 25500includes attempting to initiate a first core network signaling procedurethrough a first network access node (25502), detecting a core networkfailure for the first core network signaling procedure (25504),identifying one or more network access nodes (25506), randomly selectinga second network access node from the one or more network access nodes(25508), and attempting to initiate a second core network signalingprocedure through the second network access node (25510).

FIG. 256 shows exemplary method 25600 of operating a communicationdevice according to some aspects. As shown in FIG. 256 , method 25600includes performing a threshold number of failed connection attempts fora first radio access technology (25602), starting a timer for asubsequent connection attempt for the first radio access technology(25604), detecting that a second radio access technology hassuccessfully registered (25606), and performing the subsequentconnection attempt for the first radio access technology before thetimer expires in response to detecting that the second radio accesstechnology has successfully registered (25608).

CONCLUSION

While the above descriptions and connected figures may depict electronicdevice components as separate elements, skilled persons will appreciatethe various possibilities to combine or integrate discrete elements intoa single element. Such may include combining two or more circuits forform a single circuit, mounting two or more circuits onto a common chipor chassis to form an integrated element, executing discrete softwarecomponents on a common processor core, etc. Conversely, skilled personswill recognize the possibility to separate a single element into two ormore discrete elements, such as splitting a single circuit into two ormore separate circuits, separating a chip or chassis into discreteelements originally provided thereon, separating a software componentinto two or more sections and executing each on a separate processorcore, etc.

It is appreciated that implementations of methods detailed herein aredemonstrative in nature, and are thus understood as capable of beingimplemented in a corresponding device. Likewise, it is appreciated thatimplementations of devices detailed herein are understood as capable ofbeing implemented as a corresponding method. It is thus understood thata device corresponding to a method detailed herein may include one ormore components configured to perform each aspect of the related method.

All acronyms defined in the above description additionally hold in allclaims included herein.

The following examples pertain to further aspects of this disclosure:

Example 1 is a central trajectory controller including a cell interfaceconfigured to establish signaling connections with one or more backhaulmoving cells and to establish signaling connections with one or moreouter moving cells, an input data repository configured to obtain inputdata related to a radio environment of the one or more outer movingcells and the one or more backhaul moving cells, and a trajectoryprocessor configured to determine, based on the input data, first coarsetrajectories for the one or more backhaul moving cells and second coarsetrajectories for the one or more outer moving cells, the cell interfacefurther configured to send the first coarse trajectories to the one ormore backhaul moving cells and to send the second coarse trajectories tothe one or more outer moving cells.

In Example 2, the subject matter of Example 1 can optionally includewherein the input data includes information about data rate requirementsof the one or more outer moving cells, positions of the one or moreouter moving cells or the one or more backhaul moving cells, a targetarea assigned to the one or more outer moving cells for outer tasks,radio measurements by the one or more outer moving cells or the one ormore backhaul moving cells, or the radio capabilities of the one or moreouter moving cells or the one or more backhaul moving cells.

In Example 3, the subject matter of Example 1 or 2 can optionallyinclude wherein the input data includes radio map data for the radioenvironment.

In Example 4, the subject matter of Example 3 can optionally includewherein the input data repository is configured to generate the radiomap data or to receive the radio map data from an external network.

In Example 5, the subject matter of any one of Examples 1 to 4 canoptionally include wherein the first coarse trajectories are based on astatistical model of the radio environment, and wherein the trajectoryprocessor is configured to determine the first and second coarsetrajectories by optimizing a function of an optimization criteria asapproximated by the statistical model.

In Example 6, the subject matter of Example 5 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment.

In Example 7, the subject matter of Example 5 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment based on a radio map.

In Example 8, the subject matter of any one of Examples 5 to 7 canoptionally include wherein the optimization criteria is an aggregatesupported data rate of backhaul relaying paths between the one or moreouter moving cells and a radio access network via the one or morebackhaul moving cells, or is a probability that the supported data rateof each of the backhaul relaying paths is above a predefined data ratethreshold.

In Example 9, the subject matter of any one of Examples 5 to 7 canoptionally include wherein the optimization criteria is an aggregatelink quality metric of backhaul relaying paths between the one or moreouter moving cells and a radio access network via the one or morebackhaul moving cells, or is a probability that the link quality metricof each of the backhaul relaying paths is above a predefined linkquality metric threshold.

In Example 10, the subject matter of any one of Examples 5 to 9 canoptionally include wherein the trajectory processor is configured todetermine the first and second coarse trajectories to optimize thefunction of the optimization criteria as approximated by the statisticalmodel by optimizing the function of the optimization criteria usinggradient descent.

In Example 11, the subject matter of any one of Examples 1 to 10 canoptionally include wherein the central trajectory controller is furtherconfigured to determine initial routings between the one or more outermoving cells and a radio access network via the one or more backhaulmoving cells.

Example 12 is a method for managing trajectories for moving cells, themethod including establishing signaling connections with one morebackhaul moving cells and with one or more outer moving cells, obtaininginput data related to a radio environment of the one or more outermoving cells and the one or more backhaul moving cells, determining,based on the input data, first coarse trajectories for the one or morebackhaul moving cells and second coarse trajectories for the one or moreouter moving cells, and sending the first coarse trajectories to the oneor more backhaul moving cells and the second coarse trajectories to theone or more outer moving cells.

In Example 13, the subject matter of Example 12 can optionally includewherein the input data includes information about data rate requirementsof the one or more outer moving cells, positions of the one or moreouter moving cells or the one or more backhaul moving cells, a targetarea assigned to the one or more outer moving cells for outer tasks,radio measurements by the one or more outer moving cells or the one ormore backhaul moving cells, or the radio capabilities of the one or moreouter moving cells or the one or more backhaul moving cells.

In Example 14, the subject matter of Example 12 or 13 can optionallyinclude wherein the input data includes radio map data for the radioenvironment.

In Example 15, the subject matter of Example 14 can optionally furtherinclude generating the radio map data or receiving the radio map datafrom an external network.

In Example 16, the subject matter of any one of Examples 12 to 15 canoptionally include wherein the first coarse trajectories and the secondcoarse trajectories are based on a statistical model of the radioenvironment, wherein determining the first and second coarsetrajectories comprises determining the first and second trajectories tooptimize a function of an optimization criteria as approximated by thestatistical model.

In Example 17, the subject matter of Example 16 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment.

In Example 18, the subject matter of Example 16 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment based on a radio map.

In Example 19, the subject matter of any one of Examples 16 to 18 canoptionally include wherein the optimization criteria is an aggregatesupported data rate of backhaul relaying paths between the one or moreouter moving cells and a radio access network via the one or morebackhaul moving cells, or is a probability that the supported data rateof each of the backhaul relaying paths is above a predefined data ratethreshold.

In Example 20, the subject matter of any one of Examples 16 to 18 canoptionally include wherein the optimization criteria is an aggregatelink quality metric of backhaul relaying paths between the one or moreouter moving cells and a radio access network via the one or morebackhaul moving cells, or is a probability that the link quality metricof each of the backhaul relaying paths is above a predefined linkquality metric threshold.

In Example 21, the subject matter of any one of Examples 16 to 20 canoptionally include wherein determining the first and second coarsetrajectories to optimize the function of the optimization criteria asapproximated by the statistical model includes optimizing the functionof the optimization criteria using gradient descent.

In Example 22, the subject matter of any one of Examples 12 to 21 canoptionally include wherein determining the first coarse trajectoriesfurther includes determining initial routings between the one or moreouter moving cells and a radio access network via the one or morebackhaul moving cells.

Example 23 is a method for operating an outer moving cell, the methodincluding receiving a coarse trajectory from a central trajectorycontroller, performing an outer task when the outer moving cellestablishes a position according to the coarse trajectory, and sendingdata from the outer task to a backhaul moving cell for relay to a radioaccess network, determining an updated trajectory based on the coarsetrajectory, and performing the outer task when the outer moving cellestablishes a position according to the updated trajectory.

In Example 24, the subject matter of Example 23 can optionally includewherein performing the outer task includes performing sensing on atarget area.

In Example 25, the subject matter of Example 24 can optionally includewherein the data is sensing data.

In Example 26, the subject matter of Example 23 can optionally includewherein performing the outer task includes providing access to a targetarea.

In Example 27, the subject matter of Example 26 can optionally includewherein the data is uplink data from devices in the target area.

In Example 28, the subject matter of any one of Examples 23 to 27 canoptionally further include receiving one or more parameters from thebackhaul moving cell, wherein determining the updated trajectoryincludes determining the updated trajectory based on the coarsetrajectory and the one or more parameters.

In Example 29, the subject matter of Example 28 can optionally includewherein the one or more parameters relate to a radio environment betweenthe outer moving cell and the backhaul moving cell.

In Example 30, the subject matter of Example 28 or 29 can optionallyinclude wherein the one or more parameters include information about theposition of the backhaul moving cell, radio measurements by the backhaulmoving cell, radio capabilities of the backhaul moving cell, or a coarsetrajectory assigned to the backhaul moving cell.

In Example 31, the subject matter of any one of Examples 23 to 30 canoptionally include wherein determining the updated trajectory is basedon a statistical model of the radio environment between the outer movingcell and the backhaul moving cell, and wherein determining the updatedtrajectory includes determining the updated trajectory to optimize afunction of an optimization criteria as approximated by the statisticalmodel.

In Example 32, the subject matter of Example 31 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment.

In Example 33, the subject matter of Example 31 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment based on a radio map.

In Example 34, the subject matter of any one of Examples 31 to 33 canoptionally include wherein the optimization criteria is a supported datarate of a backhaul relaying path between the outer moving cell and theradio access network via the backhaul moving cell, or is a probabilitythat the supported data rate of the backhaul relaying path is above apredefined data rate threshold.

In Example 35, the subject matter of any one of Examples 31 to 33 canoptionally include wherein the optimization criteria is a link qualitymetric of a backhaul relaying path between the outer moving cell and theradio access network via the backhaul moving cell, or is a probabilitythat the link quality metric of the backhaul relaying path is above apredefined link quality metric threshold.

In Example 36, the subject matter of any one of Examples 31 to 35 canoptionally include wherein determining the updated trajectory tooptimize the function of the optimization criteria includes optimizingthe function of the optimization criteria using gradient descent.

In Example 37, the subject matter of any one of Examples 23 to 36 canoptionally further include receiving an updated trajectory of thebackhaul moving cell from the backhaul moving cell, determining a secondupdated trajectory based on the updated trajectory, and performing theouter task according to the second updated trajectory.

Example 38 is an outer moving cell including a central interfaceconfigured to receive a coarse trajectory from a central trajectorycontroller, an outer task engine configured to perform an outer taskwhen the outer moving cell establishes a positions according to thecoarse trajectory, a cell interface configured to send data from theouter task to a backhaul moving cell for relay to a radio accessnetwork, and a trajectory processor configured to determine an updatedtrajectory based on the coarse trajectory.

In Example 39, the subject matter of Example 38 can optionally furtherinclude steering and movement machinery configured to position the outermoving cell according to the coarse trajectory, and to position theouter moving cell according to the updated trajectory.

In Example 40, the subject matter of Example 38 or 39 can optionallyinclude wherein the outer task engine is configured to perform the outertask when the outer moving cell establishes a position according to theupdated trajectory.

In Example 41, the subject matter of any one of Examples 38 or 40 canoptionally include wherein the outer task engine includes one or moresensors, and wherein the data from the outer task is sensing data.

In Example 42, the subject matter of Example 38 or 39 can optionallyinclude wherein the outer task engine is configured to provide access toterminal devices, and wherein the data from the outer task is uplinkdata from the terminal devices.

In Example 43, the subject matter of any one of Examples 38 to 42 canoptionally include wherein the cell interface is further configured toreceive one or more parameters from the backhaul moving cell, whereinthe trajectory processor is configured to determine the updatedtrajectory based on the coarse trajectory and the one or moreparameters.

In Example 44, the subject matter of Example 43 can optionally includewherein the one or more parameters relate to a radio environment betweenthe outer moving cell and the backhaul moving cell.

In Example 45, the subject matter of Example 43 or 44 can optionallyinclude wherein the one or more parameters include information about theposition of the backhaul moving cell, radio measurements by backhaulmoving cell, or radio capabilities of the backhaul moving cell, or acoarse trajectory assigned to the backhaul moving cell.

In Example 46, the subject matter of any one of Examples 38 to 45 canoptionally include wherein the updated trajectory is based on astatistical model of the radio environment between the outer moving celland the backhaul moving cell, and wherein the trajectory processor isconfigured to determine the updated trajectory with the coarsetrajectory by determining the updated trajectory to optimize a functionof an optimization criteria as approximated by the statistical model.

In Example 47, the subject matter of Example 46 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment.

In Example 48, the subject matter of Example 46 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment based on a radio map.

In Example 49, the subject matter of any one of Examples 46 to 48 canoptionally include wherein the optimization criteria is a supported datarate of a backhaul relaying path between the outer moving cell and theradio access network via the backhaul moving cell, or is a probabilitythat the supported data rate of the backhaul relaying path is above apredefined data rate threshold.

In Example 50, the subject matter of any one of Examples 46 to 48 canoptionally include wherein the optimization criteria is a link qualitymetric of a backhaul relaying path between the outer moving cell and theradio access network via the backhaul moving cell, or is a probabilitythat the link quality metric of the backhaul relaying path is above apredefined link quality metric threshold.

In Example 51, the subject matter of any one of Examples 46 to 50 canoptionally include wherein the trajectory processor is configured todetermine the updated trajectory to optimize the function of theoptimization criteria by optimizing the function of the optimizationcriteria using gradient descent.

In Example 52, the subject matter of any one of Examples 38 to 51 canoptionally include wherein the cell interface is configured to receivean updated trajectory of the backhaul moving cell from the backhaulmoving cell, the trajectory processor is further configured to determinea second updated trajectory based on the updated trajectory of thebackhaul moving cell, and the steering and movement machinery is furtherconfigured to move the outer moving cell according to the second updatedtrajectory while the outer task engine performs the outer task.

Example 53 is a method for operating a backhaul moving cell, the methodincluding receiving a coarse trajectory from a central trajectorycontroller, receiving data from one or more outer moving cells when thebackhaul moving cell establishes a position according to the coarsetrajectory, and relaying the data to a radio access network, determiningan updated trajectory based on the coarse trajectory, and receivingadditional data from the one or more outer moving cells when thebackhaul moving cell establishes a position according to the updatedtrajectory, and relaying the additional data to the radio accessnetwork.

In Example 54, the subject matter of Example 53 can optionally furtherinclude receiving one or more parameters from the one or more outermoving cells, wherein determining the updated trajectory includesdetermining the updated trajectory based on the coarse trajectory andthe one or more parameters.

In Example 55, the subject matter of Example 54 can optionally includewherein the one or more parameters relate to a radio environment betweenthe backhaul moving cell and the one or more outer moving cells.

In Example 56, the subject matter of Example 54 or 55 can optionallyinclude wherein the one or more parameters include information about thepositions of the one or more outer moving cells, radio measurements bythe one or more outer moving cells, radio capabilities of the one ormore outer moving cells, or coarse trajectories assigned to the one ormore outer moving cells.

In Example 57, the subject matter of any one of Examples 53 to 56 canoptionally include wherein determining the updated trajectory is basedon a statistical model of the radio environment between the backhaulmoving cell and the one or more outer moving cells, and whereindetermining the updated trajectory includes determining the updatedtrajectory to optimize a function of an optimization criteria asapproximated by the statistical model.

In Example 58, the subject matter of Example 57 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment.

In Example 59, the subject matter of Example 57 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment based on a radio map.

In Example 60, the subject matter of any one of Examples 57 to 59 canoptionally include wherein the optimization criteria is an aggregatedsupported data rate of backhaul relaying paths between the one or moreouter moving cells and the radio access network via the backhaul movingcell, or a probability that the supported data rate of each of thebackhaul relaying paths is above a predefined data rate threshold.

In Example 61, the subject matter of any one of Examples 57 to 59 canoptionally include wherein the optimization criteria is an aggregatedlink quality metric of backhaul relaying paths between the one or moreouter moving cells and the radio access network via the backhaul movingcell, or a probability that the link quality metric of each of thebackhaul relaying paths is above a predefined link quality metricthreshold.

In Example 62, the subject matter of any one of Examples 57 to 61 canoptionally include wherein determining the updated trajectory tooptimize the function of the optimization criteria includes optimizingthe function of the optimization criteria using gradient descent.

In Example 63, the subject matter of any one of Examples 53 to 62 canoptionally further include receiving updated trajectories of the one ormore outer moving cells from the one or more outer moving cells,determining a second updated trajectory based on the updatedtrajectories of the one or more outer moving cells, and receiving secondadditional data from the one or more outer moving cells when thebackhaul moving cell establishes a position according to the secondupdated trajectory, and relaying the second additional data to the radioaccess network.

Example 64 is a backhaul moving cell including a central interfaceconfigured to receive a coarse trajectory from a central trajectorycontroller, a cell interface configured to receive data from one or moreouter moving cells when the backhaul moving cell establishes a positionaccording to the coarse trajectory, a relay router configured to relaythe data to a radio access network, and a trajectory processorconfigured to determine an updated trajectory based on the coarsetrajectory.

In Example 65, the subject matter of Example 64 can optionally furtherinclude steering and movement machinery configured to position thebackhaul moving cell according to the updated trajectory while the cellinterface receives additional data from the one or more outer movingcells.

In Example 66, the subject matter of Example 64 to 65 can optionallyinclude wherein the cell interface is further configured to receive oneor more parameters from the one or more outer moving cells, and whereinthe trajectory processor is configured to determine the updatedtrajectory based on the coarse trajectory and the one or moreparameters.

In Example 67, the subject matter of Example 66 can optionally includewherein the one or more parameters relate to a radio environment betweenthe backhaul moving cell and the one or more outer moving cells.

In Example 68, the subject matter of Example 66 or 67 can optionallyinclude wherein the one or more parameters include information about thepositions of the one or more outer moving cells, radio measurements bythe one or more moving outer cells, radio capabilities of the one ormore outer moving cells, or coarse trajectories assigned to the one ormore outer moving cells.

In Example 69, the subject matter of any one of Examples 64 to 68 canoptionally include wherein the updated trajectory based on a statisticalmodel of the radio environment between the backhaul moving cell and theone or more outer moving cells, and wherein the trajectory processor isconfigured to determine the updated trajectory by determining theupdated trajectory to optimize a function of an optimization criteria asapproximated by the statistical model.

In Example 70, the subject matter of Example 69 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment.

In Example 71, the subject matter of Example 69 can optionally includewherein the statistical model is a propagation model that approximatesthe radio environment based on a radio map.

In Example 72, the subject matter of any one of Examples 69 to 71 canoptionally include wherein the optimization criteria is an aggregatedsupported data rate of backhaul relaying paths between the one or moreouter moving cells and the radio access network via the backhaul movingcell, or a probability that the supported data rate of each of thebackhaul relaying paths is above a predefined data rate threshold.

In Example 73, the subject matter of any one of Examples 69 to 72 canoptionally include wherein the optimization criteria is an aggregatedlink quality metric of backhaul relaying paths between the one or moreouter moving cells and the radio access network via the backhaul movingcell, or a probability that the link quality metric of each of thebackhaul relaying paths is above a predefined link quality metricthreshold.

In Example 74, the subject matter of any one of Examples 69 to 73 canoptionally include wherein the trajectory processor is configured todetermine the updated trajectory to optimize the function of theoptimization criteria by optimizing the function of the optimizationcriteria using gradient descent.

In Example 75, the subject matter of any one of Examples 64 to 74 canoptionally include wherein the cell interface is further configured toreceive updated trajectories of the one or more outer moving cells fromthe one or more outer moving cells, the trajectory processor is furtherconfigured to determine a second updated trajectory based on the updatedtrajectories of the one or more outer moving cells, the cell interfaceis further configured to receive second additional data from the one ormore outer moving cells when the backhaul moving cell establishes aposition according to the second updated trajectory, and the relayrouter is configured to relay the second additional data to the radioaccess network.

Example 76 is a central trajectory controller including a cell interfaceconfigured to establish signaling connections with one or more backhaulmoving cells, an input data repository configured to obtain input datarelated to a radio environment of the one or more backhaul moving cellsand related to statistical density information of one or more serveddevices, and a trajectory processor configured to determine, based onthe input data, coarse trajectories for the one or more backhaul movingcells, the cell interface further configured to send the coarsetrajectories to the one or more backhaul moving cells.

In Example 77, the subject matter of Example 76 can optionally includewherein the statistical density information is statistical geographicdensity information or statistical traffic density information of theone or more served devices.

In Example 78, the subject matter of Example 76 or 77 can optionallyinclude wherein the one or more served devices include forward movingcells or terminal devices.

In Example 79, the subject matter of any one of Examples 76 to 78 canoptionally include wherein the trajectory processor is configured todetermine the coarse trajectories for the one or more backhaul movingcells by optimizing a function of an optimization criteria with astatistical model that uses the statistical density information toapproximate the one or more served devices.

Example 80 is a method for managing trajectories for moving cells, themethod including establishing signaling connections with one or morebackhaul moving cells, obtaining input data related to a radioenvironment of the one or more backhaul moving cells and related tostatistical density information of one or more served devices,determining, based on the input data, determine coarse trajectories forthe one or more backhaul moving cells, and sending the coarsetrajectories to the one or more backhaul moving cells.

In Example 81, the subject matter of Example 80 can optionally includewherein the statistical density information includes statisticalgeographic density information or statistical traffic densityinformation of the one or more served devices.

In Example 82, the subject matter of Example 80 or 81 can optionallyinclude wherein the one or more served devices include forward movingcells or terminal devices.

In Example 83, the subject matter of any one of Examples 80 to 82 canoptionally include wherein determining the coarse trajectories for theone or more backhaul moving cells includes optimizing a function of anoptimization criteria with a statistical model that uses the statisticaldensity information to approximate the one or more served devices.

Example 84 is a method for operating a backhaul moving cell, the methodincluding receiving a coarse trajectory from a central trajectorycontroller, receiving data from one or more served devices when backhaulmoving cell establishes a position according to the coarse trajectory,and relaying the data to a radio access network, determining an updatedtrajectory based on the coarse trajectory, and receiving additional datafrom the one or more served devices while positioning the backhaulmoving cell according to the updated trajectory, and relaying theadditional data to the radio access network.

In Example 85, the subject matter of Example 84 can optionally includewherein the one or more served devices include outer moving cells orterminal devices.

In Example 86, the subject matter of Example 84 or 85 can optionallyinclude wherein determining the updated trajectory includes optimizing afunction of an optimization criteria with a statistical model that usesstatistical density information to approximate the one or more serveddevices.

In Example 87, the subject matter of Example 86 can optionally includewherein the statistical density information includes statisticalgeographic density information or statistical traffic densityinformation of the one or more served devices.

Example 88 is a backhaul moving cell including a central interfaceconfigured to receive a coarse trajectory from a central trajectorycontroller, a cell interface configured to receive data from one or moreserved devices when the backhaul moving cell establishes a positionitself according to the coarse trajectory, a relay router configured torelay the data to a radio access network, and a trajectory processorconfigured to determine an updated trajectory based on the coarsetrajectory.

In Example 89, the subject matter of Example 88 can optionally furtherinclude steering and movement machinery configured to position thebackhaul moving cell according to the updated trajectory while the cellinterface receives additional data from the one or more served devices.

In Example 90, the subject matter of Example 88 or 89 can optionallyinclude wherein the one or more served devices include outer movingcells or terminal devices

In Example 91, the subject matter of any one of Examples 88 to 90 canoptionally include wherein the trajectory processor is configured todetermine the updated trajectory by optimizing a function of anoptimization criteria with a statistical model that uses statisticaldensity information to approximate the one or more served devices.

In Example 92, the subject matter of Example 91 can optionally includewherein the statistical density information includes statisticalgeographic density information or statistical traffic densityinformation of the one or more served devices.

Example 93 is a central trajectory controller including means forestablishing signaling connections with one more backhaul moving cellsand with one or more outer moving cells, means for obtaining input datarelated to a radio environment of the one or more outer moving cells andthe one or more backhaul moving cells, means for determining, based onthe input data, first coarse trajectories for the one or more backhaulmoving cells and second coarse trajectories for the one or more outermoving cells, and means for sending the first coarse trajectories to theone or more backhaul moving cells and the second coarse trajectories tothe one or more outer moving cells.

Example 94 is an outer moving cell including means for receiving acoarse trajectory from a central trajectory controller, means forperforming an outer task when the outer moving cell establishes aposition according to the coarse trajectory, means for sending data fromthe outer task to a backhaul moving cell for relay to a radio accessnetwork, means for determining an updated trajectory based on the coarsetrajectory, and means for performing the outer task when the outermoving cell establishes a position according to the updated trajectory.

Example 95 is a backhaul moving cell including means for receiving acoarse trajectory from a central trajectory controller, means forreceiving data from one or more outer moving cells when the backhaulmoving cell establishes a position according to the coarse trajectory,means for relaying the data to a radio access network, means fordetermining an updated trajectory based on the coarse trajectory, meansfor receiving additional data from the one or more outer moving cellswhen the backhaul moving cell establishes a position according to theupdated trajectory, and means for relaying the additional data to theradio access network.

Example 96 is a central trajectory controller including means forestablishing signaling connections with one or more backhaul movingcells, means for obtaining input data related to a radio environment ofthe one or more backhaul moving cells and related to statistical densityinformation of one or more served devices, means for determining, basedon the input data, coarse trajectories for the one or more backhaulmoving cells, and means for sending the coarse trajectories to the oneor more backhaul moving cells.

Example 97 is a backhaul moving cell including means for receiving acoarse trajectory from a central trajectory controller, means forreceiving data from one or more served devices when the backhaul movingcell establishes a position according to the coarse trajectory, meansfor relaying the data to a radio access network, means for determiningan updated trajectory based on the coarse trajectory, means forreceiving additional data from the one or more served devices when thebackhaul moving cell establishes a position according to the updatedtrajectory, and means for relaying the additional data to the radioaccess network.

Example 98 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of any one of Examples 12 to 37, 53 to 63, 80 to 87.

Example 99 is a device including a processor, a memory storinginstructions that, when executed by the processor, cause the processorto perform the method of any one of Examples 12 to 37, 53 to 63, 80 to87.

Example 100 is a mobile access node including a relay router configuredto relay data between one or more served terminal devices and an anchoraccess point, a local controller configured to receive controlinstructions from the anchor access point that include a coarsetrajectory and a predictable usage pattern of the one or more servedterminal devices, and a movement controller configured to control themobile access node to move based on the coarse trajectory when the relayrouter relays data between the one or more served terminal devices andthe anchor access point, wherein the local controller is furtherconfigured to update the coarse trajectory based on the predictableusage pattern to obtain an updated trajectory.

In Example 101, the subject matter of Example 100 can optionally includewhere the movement controller is further configured to control themobile access node to move based on the updated trajectory when therelay router relays data between the one or more served terminal devicesand the anchor access point.

In Example 102, the subject matter of Example 100 or 101 can optionallyfurther include steering and movement machinery, wherein the movementcontroller is configured to control the steering and movement machineryto move the mobile access node.

In Example 103, the subject matter of any one of Examples 100 to 102 canoptionally further include a baseband subsystem, a radio transceiver,and an antenna system, where the relay router is configured to relay thedata as wireless signals via the baseband subsystem, the radiotransceiver, and the antenna system.

In Example 104, the subject matter of any one of Examples 100 to 103 canoptionally include wherein the predictable usage pattern indicates apredicted user density of the one or more served terminal devices overtime, and wherein the updated trajectory corresponds to a different timeof the predictable usage pattern than the coarse trajectory.

In Example 105, the subject matter of any one of Examples 100 to 103 canoptionally include wherein the predictable usage pattern indicates apredicted user density of the one or more served terminal devices overtime, and wherein the local controller is configured to determine theupdated trajectory based on the predictable usage pattern by determininga user density with the predictable usage pattern, defining a functionof an optimization criteria based on the user density, and determining atrajectory that maximizes the function of the optimization criteria asthe updated trajectory.

In Example 106, the subject matter of Example 105 can optionally includewherein the function of the optimization criteria is part of astatistical model of the radio environment, and wherein the user densityapproximates positions of the one or more served terminal devices in thestatistical model.

In Example 107, the subject matter of any one of Examples 100 to 106 canoptionally further include a sensor configured to obtain sensing dataindicating positions of the one or more served terminal devices, and tosend the sensing data to the anchor access point, wherein thepredictable usage pattern is based on the sensing data.

In Example 108, the subject matter of any one of Examples 100 to 107 canoptionally further include a local learning subsystem, wherein the locallearning subsystem is configured to update the predictable usage patternto obtain an updated predictable usage pattern and wherein the localcontroller is configured to determine the updated trajectory based onthe updated predictable usage pattern.

In Example 109, the subject matter of Example 108 can optionally furtherinclude a sensor configured to obtain sensing data indicating positionsof the one or more served terminal devices, wherein the local learningsubsystem is configured to update the predictable usage pattern based onthe sensing data.

In Example 110, the subject matter of any one of Examples 100 to 109 canoptionally include wherein the predictable usage pattern relates to apredicted user density, predicted radio conditions, or predicted accessusage.

Example 111 is a mobile access node including a relay router configuredto relay data between one or more served terminal devices and an anchoraccess point, a sensor configured to obtain sensing data indicatingpositions of the one or more served terminal devices and to send thesensing data to the anchor access point, a local controller configuredto receive a coarse trajectory from the anchor access point that isbased on the sensing data, and a movement controller configured tocontrol the mobile access node to move based on the coarse trajectorywhen the relay router relays data between the one or more servedterminal devices and the anchor access point.

In Example 112, the subject matter of Example 111 can optionally includewherein the local controller is further configured to receive apredictable usage pattern of the one or more served terminal devicesfrom the anchor access point, and is configured to update the coarsetrajectory based on the predictable usage pattern to obtain an updatedtrajectory.

In Example 113, the subject matter of Example 112 can optionally includewherein the movement controller is further configured to control themobile access node to move based on the updated trajectory when therelay router relays data between the one or more served terminal devicesand the anchor access point.

In Example 114, the subject matter of any one of Examples 111 to 113 canoptionally further include steering and movement machinery, wherein themovement controller is configured to control the steering and movementmachinery to move the mobile access node.

In Example 115, the subject matter of any one of Examples 111 to 114 canoptionally further include a baseband subsystem, a radio transceiver,and an antenna system, where the relay router is configured to relay thedata as wireless signals via the baseband subsystem, the radiotransceiver, and the antenna system.

In Example 116, the subject matter of any one of Examples 111 to 115 canoptionally include wherein the sensing data includes radio measurements,and wherein the sensor includes a radio measurement engine configured toobtain the radio measurements by measuring wireless signals transmittedby the one or more served terminal devices.

In Example 117, the subject matter of any one of Examples 111 to 116 canoptionally include wherein the sensor includes a video sensor, an imagesensor, or a positional sensor.

Example 118 is a mobile access node including a relay router configuredto relay data between one or more served terminal devices and an anchoraccess point, a local controller configured to receive a coarsetrajectory from the anchor access point, and a movement controllerconfigured to control the mobile access node to move based on the coarsetrajectory when relaying data between the one or more served terminaldevices and the anchor access point.

Example 119 is an anchor access point including a user router configuredto exchange data with one or more served terminal devices via a mobileaccess node, a central learning subsystem configured to determine apredictable usage pattern of the one or more served terminal devicesbased on sensing data indicating positions of the one or more servedterminal devices, and a central controller configured to determine acoarse trajectory for the mobile access node based on the predictableusage pattern, and to send the coarse trajectory to the mobile accessnode.

In Example 120, the subject matter of Example 119 can optionally furtherinclude a baseband subsystem, a radio transceiver, and an antennasystem, where the user router is configured to exchange the data bywirelessly communicating the data as wireless signals via the basebandsubsystem, the radio transceiver, and the antenna system.

In Example 121, the subject matter of Example 119 or 120 can optionallyfurther include a sensor hub configured to receive the sensing data fromthe one or more served terminal devices, the mobile access node, or anexternal sensor.

In Example 122, the subject matter of any one of Examples 119 to 121 canoptionally include wherein the sensing data indicates positions of theone or more served terminal devices over a period of time, and whereinthe predictable usage pattern is based on a predicted user density overtime derived from the sensing data.

In Example 123, the subject matter of any one of Examples 119 to 122 canoptionally include wherein the predictable usage pattern indicates apredicted user density of the one or more served terminal devices, andwherein the central learning subsystem is configured to perform patternrecognition on the sensing data to learn the predicted user density ofthe one or more served terminal devices.

In Example 124, the subject matter of Example 122 or 123 can optionallyinclude wherein the predicted user density is a time-dependent densityplot that characterizes user density over time.

In Example 125, the subject matter of Example 122 or 123 can optionallyinclude wherein the predicted user density is a set of location-timepairs that identify locations and times at which heavy user densityoccurs.

In Example 126, the subject matter of any one of Examples 119 to 121 canoptionally include wherein the predictable usage pattern indicatespredicted radio conditions in a target coverage area, and wherein thecentral learning subsystem is configured to perform propagation modelingon the sensing data to learn the predicted radio conditions in thetarget coverage area.

In Example 127, the subject matter of any one of Examples 119 to 121 canoptionally include wherein the predictable usage pattern indicatespredicted access usage of the one or more served terminal devices, andwherein the central learning subsystem is configured to predict accessusage on the sensing data to learn the predicted access usage.

In Example 128, the subject matter of any one of Examples 119 to 127 canoptionally include wherein the central controller is configured todetermine the coarse trajectory for the mobile access node by using thepredictable usage pattern to model the one or more served terminaldevices as part of a statistical model of a radio environment, anddetermining the coarse trajectory to maximize a function of anoptimization criteria, where the function of the optimization criteriais based on the statistical model.

Example 129 is a mobile access node including means for relaying databetween one or more served terminal devices and an anchor access point,means for receiving control instructions from the anchor access pointthat include a coarse trajectory and a predictable usage pattern of theone or more served terminal devices, means for controlling the mobileaccess node to move based on the coarse trajectory when the means forrelaying relays data between the one or more served terminal devices andthe anchor access point, and means for updating the coarse trajectorybased on the predictable usage pattern to obtain an updated trajectory.

Example 130 is a mobile access node including means for relaying databetween one or more served terminal devices and an anchor access point,means for obtaining sensing data indicating positions of the one or moreserved terminal devices and sending the sensing data to the anchoraccess point, means for receiving a coarse trajectory from the anchoraccess point that is based on the sensing data, and means forcontrolling the mobile access node to move based on the coarsetrajectory when the means for relaying relays data between the one ormore served terminal devices and the anchor access point.

Example 131 is a mobile access node including means for relaying databetween one or more served terminal devices and an anchor access point,means for receiving a coarse trajectory from the anchor access point,and means for controlling the mobile access node to move based on thecoarse trajectory when the means for relaying relays data between theone or more served terminal devices and the anchor access point.

Example 132 is an anchor access point including means for exchangingdata with one or more served terminal devices via a mobile access node,means for determining a predictable usage pattern of the one or moreserved terminal devices based on sensing data indicating positions ofthe one or more served terminal devices, means for determining a coarsetrajectory for the mobile access node based on the predictable usagepattern and sending the coarse trajectory to the mobile access node.

Example 133 is a method of operating a mobile access node, the methodincluding relaying data between one or more served terminal devices andan anchor access point, receiving control instructions from the anchoraccess point that include a coarse trajectory and a predictable usagepattern of the one or more served terminal devices, controlling themobile access node to move based on the coarse trajectory when relayingdata between the one or more served terminal devices and the anchoraccess point, and updating the coarse trajectory based on thepredictable usage pattern to obtain an updated trajectory.

In Example 134, the subject matter of Example 133 can optionally furtherinclude controlling the mobile access node to move based on the updatedtrajectory when relaying data between the one or more served terminaldevices and the anchor access point.

In Example 135, the subject matter of Example 133 or 134 can optionallyinclude wherein controlling the mobile access node to move includescontrolling steering and movement machinery of the mobile access node tomove the mobile access node.

In Example 136, the subject matter of any one of Examples 133 to 135 canoptionally include wherein relaying the data between the one or moreserved terminal devices and the anchor access point includes relayingthe data as wireless signals.

In Example 137, the subject matter of any one of Examples 133 to 136 canoptionally include wherein the predictable usage pattern indicates apredicted user density of the one or more served terminal devices overtime, and wherein the updated trajectory corresponds to a different timeof the predictable usage pattern than the coarse trajectory.

In Example 138, the subject matter of any one of Examples 133 to 136 canoptionally include wherein the predictable usage pattern indicates apredicted user density of the one or more served terminal devices overtime, and wherein determining the updated trajectory based on thepredictable usage pattern includes determining a user density with thepredictable usage pattern, defining a function of an optimizationcriteria based on the user density, and determining a trajectory thatmaximizes the function of the optimization criteria as the updatedtrajectory.

In Example 139, the subject matter of any one of Examples the functionof can optionally include optimization criteria is part of a statisticalmodel of the radio environment and wherein the user density approximatespositions of the one or more served terminal devices in the statisticalmodel.

In Example 140, the subject matter of any one of Examples 133 to 139 canoptionally further include obtaining sensing data indicating positionsof the one or more served terminal devices, and sending the sensing datato the anchor access point, wherein the predictable usage pattern isbased on the sensing data.

In Example 141, the subject matter of any one of Examples 133 to 140 canoptionally further include updating the predictable usage pattern toobtain an updated predictable usage pattern, wherein determining theupdated trajectory includes determining the updated trajectory based onthe updated predictable usage pattern.

In Example 142, the subject matter of Example 141 can optionally furtherinclude obtaining sensing data indicating positions of the one or moreserved terminal devices, wherein updating the predictable usage patternincludes updating the predictable usage pattern based on the sensingdata.

In Example 143, the subject matter of any one of Examples 133 to 142 canoptionally include wherein the predictable usage pattern relates to apredicted user density, prediction radio conditions, or predicted accessusage.

Example 144 is a method of operating a mobile access node, the methodincluding relaying data between one or more served terminal devices andan anchor access point, obtaining sensing data indicating positions ofthe one or more served terminal devices and sending the sensing data tothe anchor access point, receiving a coarse trajectory from the anchoraccess point that is based on the sensing data, and controlling themobile access node to move based on the coarse trajectory when relayingdata between the one or more served terminal devices and the anchoraccess point.

In Example 145, the subject matter of Example 144 can optionally furtherinclude receiving a predictable usage pattern of the one or more servedterminal devices from the anchor access point, and updating the coarsetrajectory based on the predictable usage pattern to obtain an updatedtrajectory.

In Example 146, the subject matter of Example 145 can optionally furtherinclude controlling the mobile access node to move based on the updatedtrajectory when relaying data between the one or more served terminaldevices and the anchor access point.

In Example 147, the subject matter of any one of Examples 144 to 146 canoptionally include wherein controlling the mobile access node to moveincludes controlling steering and movement machinery of the mobileaccess node to move the mobile access node.

In Example 148, the subject matter of any one of Examples 144 to 147 canoptionally include wherein relaying the data between the one or moreserved terminal devices and the anchor access point includes relayingthe data as wireless signals.

In Example 149, the subject matter of any one of Examples 144 to 148 canoptionally include wherein the sensing data includes radio measurements,and wherein obtaining the sensing data includes measuring wirelesssignals transmitted by the one or more served terminal devices.

Example 150 is a method of operating a mobile access node, the methodincluding relaying data between one or more served terminal devices andan anchor access point, receiving a coarse trajectory from the anchoraccess point, and controlling the mobile access node to move based onthe coarse trajectory when relaying data between the one or more servedterminal devices and the anchor access point.

Example 151 is a method of operating an anchor access point, the methodincluding exchanging data with one or more served terminal devices via amobile access node, determining a predictable usage pattern of the oneor more served terminal devices based on sensing data indicatingpositions of the one or more served terminal devices, and determining acoarse trajectory for the mobile access node based on the predictableusage pattern, and sending the coarse trajectory to the mobile accessnode.

In Example 152, the subject matter of Example 151 can optionally includewherein exchanging the data with the one or more served terminal devicesvia the mobile access node includes wirelessly communicating the data aswireless signals.

In Example 153, the subject matter of Example 151 or 152 can optionallyfurther include receiving the sensing data from the one or more servedterminal devices, the mobile access node, or an external sensor.

In Example 154, the subject matter of any one of Examples 151 to 153 canoptionally include wherein the sensing data indicates positions of theone or more served terminal devices over a period of time, and whereinthe predictable usage pattern is based on a predicted user density overtime derived from the sensing data.

In Example 155, the subject matter of any one of Examples 151 to 154 canoptionally include wherein the predictable usage pattern indicates apredicted user density of the one or more served terminal devices, themethod further including performing pattern recognition on the sensingdata to learn the predicted user density of the one or more servedterminal devices.

In Example 156, the subject matter of Example 154 or 155 can optionallyinclude wherein the predicted user density is a time-dependent densityplot that characterizes user density over time.

In Example 157, the subject matter of Example 154 or 155 can optionallyinclude wherein the predicted user density is a set of location-timepairs that identify locations and times at which heavy user densityoccurs.

In Example 158, the subject matter of any one of Examples 151 to 153 canoptionally include wherein the predictable usage pattern indicatespredicted radio conditions in a target coverage area, the method furtherincluding performing propagation modeling on the sensing data to learnthe predicted radio conditions in the target coverage area.

In Example 159, the subject matter of any one of Examples 151 to 153 canoptionally include wherein the predictable usage pattern indicatespredicted access usage of the one or more served terminal devices, themethod further including performing access usage prediction on thesensing data to learn the predicted access usage.

In Example 160, the subject matter of any one of Examples 151 to 159 canoptionally include wherein determining the coarse trajectory for themobile access node includes using the predictable usage pattern to modelthe one or more served terminal devices as part of a statistical modelof a radio environment, and determining the coarse trajectory tomaximize a function of an optimization criteria, where the function ofthe optimization criteria is based on the statistical model.

Example 161 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of any one of Examples 133 to 160.

Example 162 is a communication device including a processor, and amemory storing instructions that when executed by the processor causethe communication device to perform the method of any one of Examples133 to 160.

Example 163 is a central trajectory controller including a trajectoryprocessor configured to determine a coarse trajectory for a mobileaccess node based on a function of a radio link optimization criteria,wherein the function of the radio link optimization criteriaapproximates a radio link optimization criteria for different coarsetrajectories and is based on propagation pathloss data for an outersurface of an indoor coverage area, and a node interface configured tosend the coarse trajectory to the mobile access node.

In Example 164, the subject matter of Example 163 can optionally includewherein the function of the radio link optimization criteria is based ona statistical model of a radio environment around the indoor coveragearea, and wherein the propagation pathloss data characterizespropagation pathloss of radio signals passing through the outer surfacein the statistical model.

In Example 165, the subject matter of Example 163 or 164 can optionallyfurther include a central learning subsystem configured to receive radiomeasurements originating from around the indoor coverage area, and toupdate the propagation pathloss data based on the radio measurements toobtain updated propagation pathloss data.

In Example 166, the subject matter of Example 165 can optionally includewherein the trajectory processor is configured to determine an updatedtrajectory for the mobile access node based on the updated propagationpathloss data, and wherein the node interface is configured to send theupdated trajectory to the mobile access node.

In Example 167, the subject matter of Example 163 or 164 can optionallyfurther include a central learning subsystem configured to receive radiomeasurements originating from around the indoor coverage area, and togenerate the propagation pathloss data based on the radio measurements.

In Example 168, the subject matter of Example 167 can optionally includewherein the radio measurements are paired with geotagged locationinformation about a transmitting or receiving device for the radiomeasurements, and wherein the central learning subsystem is configuredto generate the propagation pathloss data by estimating the propagationpathloss at location on the outer surface based on the radiomeasurements and the geotagged location information.

In Example 169, the subject matter of any one of Examples 163 to 168 canoptionally include wherein the trajectory processor is configured todetermine the coarse trajectory by determining a coarse trajectory thatincreases the function of the optimization criteria.

In Example 170, the subject matter of any one of Examples 163 to 169 canoptionally include wherein the function of the radio link optimizationcriteria is a statistical expression that approximates a supported datarate of radio links between served terminal devices in the indoorcoverage area and the mobile access node, approximates a probabilitythat the supported data rate of each of the radio links is above asupported data rate threshold, approximates a link quality metric ofradio links between the served terminal devices and the mobile accessnode, or approximates a probability that the link quality metric of eachradio link is above a link quality metric threshold.

In Example 171, the subject matter of any one of Examples 163 to 170 canoptionally include wherein the node interface is configured to use asignaling connection through a radio access network to send the coarsetrajectory to the mobile access node.

Example 172 is a mobile access node including a relay router configuredto relay data between a served terminal device in an indoor coveragearea and a radio access network, and a local controller configured todetermine a trajectory based on a function of a radio link optimizationcriteria, where the function of the radio link optimization criteria isbased on propagation pathloss data for an outer surface of the indoorcoverage area and approximates a radio link optimization criteria fordifferent trajectories, the relay router further configured to relaydata between the served terminal device and the radio access networkwhile the mobile access node moves according to the trajectory.

In Example 173, the subject matter of Example 172 can optionally furtherinclude one or more antennas, a radio frequency (RF) transceiver, and abaseband modem, where the relay router is configured to transmit andreceive data as wireless signals via the one or more antennas, the RFtransceiver, and the baseband modem.

In Example 174, the subject matter of Example 172 can optionally furtherinclude a movement controller and steering and movement machinery, wheremovement controller is configured to control the steering and movementmachinery to move the mobile access node according to the trajectorywhile the relay router relays data between the served terminal deviceand the radio access network.

In Example 175, the subject matter of any one of Examples 172 to 174 canoptionally include wherein the function of the radio link optimizationcriteria is based on a statistical model of a radio environment aroundthe indoor coverage area, and wherein the propagation pathloss datacharacterizes propagation pathloss of radio signals passing through theouter surface in the statistical model.

In Example 176, the subject matter of any one of Examples 172 to 175 canoptionally further include a local learning engine configure to receiveradio measurements from around the indoor coverage area, and to updatethe propagation pathloss data based on the radio measurements to obtainupdated propagation pathloss data.

In Example 177, the subject matter of Example 176 can optionally includewherein the local controller is configured to determine an updatedtrajectory for the mobile access node based on the updated propagationpathloss data, and wherein the relay router is configured to relay databetween the served terminal device and the radio access network whilethe mobile access node moves according to the updated trajectory.

In Example 178, the subject matter of any one of Examples 172 to 175 canoptionally further include a local learning engine configured to receiveradio measurements originating from around the indoor coverage area, andto generate the propagation pathloss data based on the radiomeasurements.

In Example 179, the subject matter of Example 178 can optionally includewherein the radio measurements are paired with geotagged locationinformation about a transmitting or receiving device for the radiomeasurements, and wherein the central learning subsystem is configuredto generate the propagation pathloss data by estimating the propagationpathloss at allocation on the outer surface based on the radiomeasurements and the geotagged location information.

In Example 180, the subject matter of any one of Examples 172 to 179 canoptionally include wherein the local controller is configured todetermine the trajectory by determining a trajectory that increases thefunction of the optimization criteria.

In Example 181, the subject matter of any one of Examples 172 to 180 canoptionally include wherein the function of the radio link optimizationcriteria is a statistical expression that approximates a supported datarate of radio links between served terminal devices in the indoorcoverage area and the mobile access node, approximates a probabilitythat the supported data rate of each of the radio links is above asupported data rate threshold, approximates a link quality metric ofradio links between the served terminal devices and the mobile accessnode, or approximates a probability that the link quality metric of eachradio link is above a link quality metric threshold.

In Example 182, the subject matter of any one of Examples 172 to 181 canoptionally include wherein the local controller is further configured todetermine a beamsteering direction based on the propagation pathlossdata, the mobile access node further including one or more antennasconfigured to wirelessly transmit the data for the relay routeraccording to the beamsteering direction.

In Example 183, the subject matter of Example 182 can optionally includewherein the local controller is configured to determine the beamsteeringdirection by determining a beamsteering direction that increases thefunction of the optimization criteria.

In Example 184, the subject matter of Example 182 can optionally includewherein the propagation pathloss data identifies one or more lowpropagation pathloss areas of the outer surface, and wherein the localcontroller is configured to determine the beamsteering direction bydetermining a beamsteering direction that yields an antenna beam thatpasses through one of the one or more low propagation pathloss areas.

Example 185 is a mobile access node including a relay router configuredto relay data between a served terminal device in an indoor coveragearea and a radio access network, and a local controller configured touse a function of a radio link optimization criteria to determine atrajectory, where the function of the radio link optimization criteriais based on surface propagation pathloss data of an outer surface of theindoor coverage area, the relay router further configured to relay databetween the served terminal device and the radio access network whilethe mobile access node moves according to the trajectory.

Example 186 is a central trajectory controller including a trajectoryprocessor configured to estimate an amount of bandwidth for supportingdata usage by served terminal devices in an indoor coverage area,determine a number of mobile access nodes to deploy to serve the indoorcoverage area based on the amount of bandwidth, and select one or moremobile access nodes based on the number, and a node interface configuredto send signaling to the one or more mobile access nodes to activate theone or mobile access nodes.

In Example 187, the subject matter of Example 186 can optionally includewherein the trajectory processor is configured to estimate the amount ofbandwidth for supporting the data usage based on context informationthat indicates a number of served terminal devices in the indoorcoverage area or that indicates overall or individual data usage byserved terminal devices in the indoor coverage area.

In Example 188, the subject matter of Example 186 or 187 can optionallyinclude wherein the trajectory processor is configured to determine thenumber of mobile access nodes to deploy based on the amount of bandwidthand a redundancy parameter that increases the number of mobile accessnodes to deploy.

In Example 189, the subject matter of any one of Examples 186 to 188 canoptionally include wherein the trajectory processor is configured toselect the one or more mobile access nodes from a fleet of mobile accessnodes available for serving the indoor coverage area.

In Example 190, the subject matter of any one of Examples 186 to 189 canoptionally include wherein the trajectory processor is configured toselect the one or more mobile access nodes by selecting mobile accessnodes equal in quantity to the number of mobile access nodes.

In Example 191, the subject matter of any one of Examples 186 to 190 canoptionally include wherein the node interface is configured to use asignaling connection through a radio access network to send thesignaling to the one or more mobile access nodes.

Example 192 is a central trajectory controller including a trajectoryprocessor configured to estimate an capacity requirement of servedterminal devices in an indoor coverage area, determine a number ofmobile access nodes to deploy to serve the indoor coverage area based onthe amount of bandwidth, and select one or more mobile access nodesbased on the number, and a node interface configured to send signalingto the one or more mobile access nodes to activate the one or mobileaccess nodes.

Example 193 is a method of operating a central trajectory controller,the method including determining a coarse trajectory for a mobile accessnode based on a function of a radio link optimization criteria, whereinthe function of the radio link optimization criteria is based onpropagation pathloss data for an outer surface of an indoor coveragearea and approximates a radio link optimization criteria for differentcoarse trajectories, sending the coarse trajectory to the mobile accessnode.

In Example 194, the subject matter of Example 193 can optionally includewherein the function of the radio link optimization criteria is based ona statistical model of a radio environment around the indoor coveragearea, and wherein the propagation pathloss data characterizespropagation pathloss of radio signals passing through the outer surfacein the statistical model.

In Example 195, the subject matter of Example 193 or 194 can optionallyfurther include receiving radio measurements originating from around theindoor coverage area and updating the propagation pathloss data based onthe radio measurements to obtain updated propagation pathloss data.

In Example 196, the subject matter of Example 195 can optionally furtherinclude determining an updated trajectory for the mobile access nodebased on the propagation pathloss data and sending the updatedtrajectory to the mobile access node.

In Example 197, the subject matter of Example 193 or 194 can optionallyfurther include receiving radio measurements originating from around theindoor coverage area and generating the propagation pathloss data basedon the radio measurements.

In Example 198, the subject matter of Example 197 can optionally includewherein the radio measurements are paired with geotagged locationinformation about a transmitting or receiving device for the radiomeasurements, wherein generating the propagation pathloss data based onthe radio measurements includes estimating the propagation pathloss atlocation on the outer surface based on the radio measurements and thegeotagged location information.

In Example 199, the subject matter of any one of Examples 193 to 198 canoptionally include wherein determining the coarse trajectory includesdetermining a coarse trajectory that increases the function of theoptimization criteria.

In Example 200, the subject matter of any one of Examples 193 to 199 canoptionally include wherein the function of the radio link optimizationcriteria is a statistical expression that approximates a supported datarate of radio links between served terminal devices in the indoorcoverage area and the mobile access node, approximates a probabilitythat the supported data rate of each of the radio links is above asupported data rate threshold, approximates a link quality metric ofradio links between the served terminal devices and the mobile accessnode, or approximates a probability that the link quality metric of eachradio link is above a link quality metric threshold.

In Example 201, the subject matter of any one of Examples 193 to 200 canoptionally include wherein sending the coarse trajectory to the mobileaccess node includes sending the coarse trajectory on a signalingconnection through a radio access network to the mobile access node.

Example 202 is a method of operating a mobile access node, the methodincluding relaying data between a served terminal device in an indoorcoverage area and a radio access network, determining a trajectory basedon a function of a radio link optimization criteria, where the functionof the radio link optimization criteria is based on propagation pathlossdata for an outer surface of the indoor coverage area and approximates aradio link optimization criteria for different trajectories, relayingdata between the served terminal device and the radio access networkwhile moving the mobile access node according to the trajectory.

In Example 203, the subject matter of Example 202 can optionally includewherein moving the mobile access node according to the trajectoryincludes controlling steering and movement machinery of the mobileaccess node to move the mobile access node.

In Example 204, the subject matter of Example 202 or 203 can optionallyinclude wherein the function of the radio link optimization criteria isbased on a statistical model of a radio environment around the indoorcoverage area, and wherein the propagation pathloss data characterizespropagation pathloss of radio signals passing through the outer surfacein the statistical model.

In Example 205, the subject matter of any one of Examples 202 to 204 canoptionally further include receiving radio measurements originating fromaround the indoor coverage area and updating the propagation pathlossdata based on the radio measurements to obtain updated propagationpathloss data.

In Example 206, the subject matter of Example 205 can optionally furtherinclude determining an updated trajectory for the mobile access nodebased on the updated propagation pathloss data, and relaying databetween the served terminal device and the radio access network whilemoving the mobile access node according to the updated trajectory.

In Example 207, the subject matter of any one of Examples 202 to 204 canoptionally further include receiving radio measurements originating fromaround the indoor coverage area and generating the propagation pathlossdata based on the radio measurements.

In Example 208, the subject matter of Example 207 can optionally includewherein the radio measurements are paired with geotagged locationinformation about a transmitting or receiving device for the radiomeasurements, wherein generating the propagation pathloss data includesestimating the propagation pathloss at allocation on the outer surfacebased on the radio measurements and the geotagged location information.

In Example 209, the subject matter of any one of Examples 202 to 208 canoptionally include wherein determining the trajectory includesdetermining a trajectory that increases the function of the optimizationcriteria.

In Example 210, the subject matter of any one of Examples 202 to 209 canoptionally further include determining a beamsteering direction based onthe propagation pathloss data, wherein relaying the data between theserved terminal device and the radio access network includes wirelesslytransmitting the data according to the beamsteering direction.

In Example 211, the subject matter of Example 210 can optionally includewherein determining the beamsteering direction includes determining abeamsteering direction that increases the function of the optimizationcriteria.

In Example 212, the subject matter of Example 210 can optionally includewherein the propagation pathloss data identifies one or more lowpropagation pathloss areas of the outer surface, and wherein determiningthe beamsteering direction includes determining a beamsteering directionthat yields an antenna beam that passes through one of the one or morelow propagation pathloss areas.

Example 213 is a method of operating a mobile access node, the methodincluding relaying data between a served terminal device in an indoorcoverage area and a radio access network, using a function of a radiolink optimization criteria to determine a trajectory, where the functionof the radio link optimization criteria is based on surface propagationpathloss data of an outer surface of the indoor coverage area, andrelaying data between the served terminal device and the radio accessnetwork while moving the mobile access node according to the trajectory.

Example 214 is a method of operating a central trajectory controller,the method including estimating an amount of bandwidth for supportingdata usage by served terminal devices in an indoor coverage area,determining a number of mobile access nodes to deploy to serve theindoor coverage area based on the amount of bandwidth, selecting one ormore mobile access nodes based on the number, and sending signaling tothe one or more mobile access nodes to activate the one or mobile accessnodes.

In Example 215, the subject matter of Example 214 can optionally includewherein estimating the amount of bandwidth includes estimating theamount of bandwidth for supporting the data usage based on contextinformation that indicates a number of served terminal devices in theindoor coverage area or that indicates overall or individual data usageby served terminal devices in the indoor coverage area.

In Example 216, the subject matter of Example 214 or 215 can optionallyinclude wherein determining the number of mobile access nodes to deployincludes determining the number of mobile access nodes to deploy basedon the amount of bandwidth and a redundancy parameter that increases thenumber of mobile access nodes to deploy.

In Example 217, the subject matter of any one of Examples 214 to 216 canoptionally include wherein selecting the one or more mobile access nodesincludes selecting the one or more mobile access nodes from a fleet ofmobile access nodes available for serving the indoor coverage area.

In Example 218, the subject matter of any one of Examples 214 to 217 canoptionally include wherein selecting the one or more mobile access nodesincludes selecting mobile access nodes equal in quantity to the numberof mobile access nodes.

In Example 219, the subject matter of any one of Examples 214 to 218 canoptionally include wherein sending the signaling to the one or moremobile access nodes includes sending the signaling to the one or moremobile access nodes over a signaling connection through a radio accessnetwork.

Example 220 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 193 to219.

Example 221 is a device including one or more processors, and a memorystoring instructions that when executed by the one or more processorscause the one or more processors to perform the method of any one ofExamples 193 to 219.

Example 222 is a central trajectory controller including determiningmeans configured to determine a coarse trajectory for a mobile accessnode based on a function of a radio link optimization criteria, whereinthe function of the radio link optimization criteria is based onpropagation pathloss data for an outer surface of an indoor coveragearea and approximates a radio link optimization criteria for differentcoarse trajectories, sending means configured to send the coarsetrajectory to the mobile access node.

Example 223 is a mobile access node including relaying means configuredto relay data between a served terminal device in an indoor coveragearea and a radio access network, and determining means configured todetermine a trajectory based on a function of a radio link optimizationcriteria, where the function of the radio link optimization criteria isbased on propagation pathloss data for an outer surface of the indoorcoverage area and approximates a radio link optimization criteria fordifferent trajectories, the relaying means further configured to relaydata between the served terminal device and the radio access networkwhile moving the mobile access node according to the trajectory.

Example 224 is a mobile access node including relaying means configuredto relay data between a served terminal device in an indoor coveragearea and a radio access network, and determining means configured to usea function of a radio link optimization criteria to determine atrajectory, where the function of the radio link optimization criteriais based on surface propagation pathloss data of an outer surface of theindoor coverage area, the relaying means further configured to relaydata between the served terminal device and the radio access networkwhile moving the mobile access node according to the trajectory.

Example 225 is a central trajectory controller including estimatingmeans configured to estimate an amount of bandwidth for supporting datausage by served terminal devices in an indoor coverage area, determiningmeans configured to determine a number of mobile access nodes to deployto serve the indoor coverage area based on the amount of bandwidth,selecting means configured to select one or more mobile access nodesbased on the number, and sending means configured to send signaling tothe one or more mobile access nodes to activate the one or mobile accessnodes.

Example 226 is a terminal device including a resource platform includinghardware resources for computing, storage, or networking, a functioncontroller configured to receive an allocation of a virtualized functionfrom a virtual cell, and to configure the resource platform for thevirtualized function, the resource platform configured to perform thevirtualized function to obtain result data, and to send the result datato another terminal device of the virtual cell.

In Example 227, the subject matter of Example 226 can optionally includewherein the virtualized function is a virtualized function for thevirtual cell.

In Example 228, the subject matter of Example 226 can optionally includewherein the resource platform includes compute resources, storageresources, or network resources that are logically designated as part ofa resource pool for the virtual cell.

In Example 229, the subject matter of Example 226 or 228 can optionallyinclude wherein the function controller is configured to configure theresource platform for the virtualized function by loading software ontoone or more processors of the resource platform.

In Example 230, the subject matter of any one of Examples 226 to 229 canoptionally further include a baseband modem, wherein the functioncontroller is configured to wirelessly receive the allocation via thebaseband modem.

In Example 231, the subject matter of any one of Examples 226 to 230 canoptionally include wherein the virtualized function is a cell processingvirtualized function or a radio activity virtualized function.

In Example 232, the subject matter of any one of Examples 226 to 231 canoptionally include wherein the virtualized function is an uplink ordownlink processing virtualized function, and wherein the resourceplatform is configured to send the result data to another uplink ordownlink processing virtualized function running of the another terminaldevice.

In Example 233, the subject matter of any one of Examples 226 to 232 canoptionally include wherein the function controller is configured toreceive the allocation of the virtualized function from a virtualizedfunction manager of the virtual cell.

Example 234 is a terminal device including a resource platform includinghardware resources for computing, storage, or networking, a functioncontroller configured to receive an allocation of a virtualized functionfrom a virtual cell, and to configure the resource platform for thevirtualized function, the resource platform configured to perform thevirtualized function to provide a cell processing function or a radioactivity function for a terminal device served by the virtual cell.

In Example 235, the subject matter of Example 234 can optionally includewherein the virtualized function is a virtualized function for thevirtual cell.

In Example 236, the subject matter of Example 234 can optionally includewherein the virtualized function is a downlink processing virtualizedfunction, and wherein the resource platform is configured to processdownlink data, addressed to the terminal device, according to thedownlink processing virtualized function to obtain result data.

In Example 237, the subject matter of Example 236 can optionally includewherein the resource platform is configured to send the result data toanother downlink processing virtualized function of the virtual cell.

In Example 238, the subject matter of Example 237 can optionally includewherein the other downlink processing virtualized function is executableat another terminal device of the virtual cell.

In Example 239, the subject matter of Example 236 can optionally includewherein the downlink processing virtualized function is a downlinkphysical layer processing virtualized function, and wherein the resourceplatform is configured to wirelessly transmit the result data to theterminal device.

In Example 240, the subject matter of Example 234 can optionally includewherein the virtualized function is an uplink processing virtualizedfunction, and wherein the resource platform is configured to processuplink data, originating from the terminal device, according to theuplink processing virtualized function to obtain result data.

In Example 241, the subject matter of Example 240 can optionally includewherein the resource platform is configured to send the result data toanother uplink processing virtualized function of the virtual cell.

In Example 242, the subject matter of Example 241 can optionally includewherein the other uplink processing virtualized function is running atanother terminal device of the virtual cell.

In Example 243, the subject matter of Example 240 can optionally includewherein the resource platform is configured to wirelessly transmit theresult data to a radio access network over a backhaul link.

In Example 244, the subject matter of any one of Examples 234 to 243 canoptionally include wherein the virtualized function is also allocated toa resource platform of another terminal device of the virtual cell, andwherein the resource platform is configured to perform the virtualizedfunction in cooperation with the resource platform of the other terminaldevice.

In Example 245, the subject matter of any one of Examples 234 to 244 canoptionally include wherein the resource platform includes computeresources, storage resources, or network resources that are logicallydesignated as part of a resource pool for the virtual cell.

In Example 246, the subject matter of any one of Examples 234 to 244 canoptionally further include a baseband modem, wherein the functioncontroller is configured to wirelessly receive the allocation via thebaseband modem.

In Example 247, the subject matter of any one of Examples 234 to 246 canoptionally further include a radio frequency transceiver and one or moreantennas.

Example 248 is a terminal device including a resource platform includinghardware resources for computing, storage, or networking, a controllerconfigured to receive an allocation of a virtualized function from avirtual cell, and to configure the resource platform for the virtualizedfunction, the resource platform configured to perform the virtualizedfunction in cooperation with a resource platform of another terminaldevice of the virtual cell.

Example 249 is a terminal device including a function controllerconfigured to identify a virtualized function that uses resourceplatforms of multiple terminal devices of a virtual cell, identify aplurality of terminal devices of the virtual cell based on wirelesslinks between the plurality of terminal devices, and allocate thevirtualized function to the plurality of terminal devices for executionin a distributed manner.

In Example 250, the subject matter of Example 249 can optionally includewherein the virtualized function is configured for distributed executionat resource platforms of multiple terminal devices, or is configured touse result data from a counterpart virtualized function executable onanother terminal device.

In Example 251, the subject matter of Example 249 or 250 can optionallyinclude wherein the function controller is configured to evaluate radiomeasurements that characterize the wireless links between the pluralityof terminal devices, and to identify the plurality of terminal devicesbased on a strength of the radio measurements.

In Example 252, the subject matter of Example 249 or 250 can optionallyinclude wherein the function controller is configured to evaluatepositions of the plurality of terminal devices, and to identify theplurality of terminal devices based on a relative proximity indicated bytheir positions.

In Example 253, the subject matter of any one of Examples 249 to 252 canoptionally include wherein the function controller is configured todetermine a number of terminal devices that the virtualized functionuses, and to select a plurality of terminal devices of the virtual cellequal in quantity to the number as the plurality of terminal devices.

In Example 254, the subject matter of any one of Examples 249 to 253 canoptionally further include a baseband modem, wherein the functioncontroller is configured to transmit an allocation of the virtualizedfunction to the plurality of terminal devices via the baseband modem.

Example 255 is a terminal device including a function controllerconfigured to communicate with terminal devices of a virtual cell, aresource platform configured to execute a master terminal devicevirtualized function for the virtual cell in cooperation with a resourceplatform of another terminal device of the virtual cell, identify avirtualized function that uses resource platforms of multiple terminaldevices of the virtual cell, identify a plurality of terminal devices ofthe virtual cell based on wireless links between the plurality ofterminal devices, and allocate the virtualized function to the pluralityof terminal devices for execution in a distributed manner.

Example 256 is a terminal device including a function controllerconfigured to identify a virtualized function that uses resourceplatforms of multiple terminal devices of a virtual network, identify aplurality of terminal devices of the virtual network based on wirelesslinks between the plurality of terminal devices, and allocate thevirtualized function to the plurality of terminal devices for executionin a distributed manner.

Example 257 is a terminal device including a function controllerconfigured to communicate with terminal devices of a virtual network,and a resource platform configured to execute a master terminal devicevirtualized function for the virtual network in cooperation with aresource platform of another terminal device of the virtual network,identify a virtualized function that uses resource platforms of multipleterminal devices of the virtual network, identify a plurality ofterminal devices of the virtual network based on wireless links betweenthe plurality of terminal devices, and allocate the virtualized functionto the plurality of terminal devices for execution in a distributedmanner.

Example 258 is a terminal device including a function controllerconfigured to identify, for each of a plurality of virtualizedfunctions, one or more terminal devices of a virtual cell, allocate eachof the plurality of virtualized functions to the corresponding one ormore terminal devices.

Example 259 is a terminal device including a function controllerconfigured to exchange signaling with one or more terminal devices tojoin a virtual network, and to receive an allocation for a virtualizedfunction from a virtualized function manager of the virtual network, anda resource platform configured to virtually perform the virtualizedfunction in cooperation with a resource platform of another terminaldevice of the virtual network.

Example 260 is a virtual cell including a plurality of terminal devicesincluding function controllers and resource platforms, a virtualizedfunction manager configured to allocate a plurality of virtualizedfunctions between the plurality of terminal devices, wherein theplurality of terminal devices are configured to provide radio access toone or more served terminal devices by performing the respectivelyallocated virtualized functions at their respective resource platforms.

Example 261 is a method of operating a terminal device, the methodincluding receiving an allocation of a virtualized function from avirtual cell, configuring a resource platform of the terminal device forthe virtualized function, performing the virtualized function with theresource platform to obtain result data, and sending the result data toanother terminal device of the virtual cell.

In Example 262, the subject matter of Example 261 can optionally includewherein the resource platform includes compute resources, storageresources, or network resources that are logically designated as part ofa resource pool for the virtual cell.

In Example 263, the subject matter of Example 261 or 262 can optionallyinclude wherein configuring the resource platform for the virtualizedfunction includes loading software onto one or more processors of theresource platform.

In Example 264, the subject matter of any one of Examples 261 to 263 canoptionally include wherein receiving the allocation includes wirelesslyreceiving the allocation via a baseband modem of the terminal device.

In Example 265, the subject matter of any one of Examples 261 to 264 canoptionally include wherein the virtualized function is a cell processingvirtualized function or a radio activity virtualized function.

In Example 266, the subject matter of any one of Examples 261 to 265 canoptionally include wherein the virtualized function is an uplink ordownlink processing virtualized function, and wherein sending the resultdata includes sending the result data to another uplink or downlinkprocessing virtualized function running on the other terminal device.

Example 267 is a method of operating a terminal device, the methodincluding receiving an allocation of a virtualized function from avirtual cell, configuring a resource platform of the terminal devicewith software for performing the virtualized function, and performingthe virtualized function to provide a cell processing function or aradio activity function for a terminal device served by the virtualcell.

In Example 268, the subject matter of Example 267 can optionally includewherein the virtualized function is a downlink processing virtualizedfunction, and wherein performing the virtualized function includesprocessing downlink data, addressed to the terminal device, according tothe downlink processing virtualized function to obtain result data.

In Example 269, the subject matter of Example 268 can optionally furtherinclude sending the result data to another downlink processingvirtualized function of the virtual cell.

In Example 270, the subject matter of Example 269 can optionally includewherein the other downlink processing virtualized function is running atanother terminal device of the virtual cell.

In Example 271, the subject matter of Example 268 can optionally includewherein the downlink processing virtualized function is a downlinkphysical layer processing virtualized function, the method furtherincluding wirelessly transmitting the result data to the terminaldevice.

In Example 272, the subject matter of Example 267 can optionally includewherein the virtualized function is an uplink processing virtualizedfunction, and wherein performing the virtualized function includesprocessing uplink data, originating from the terminal device, accordingto the uplink processing virtualized function to obtain result data.

In Example 273, the subject matter of Example 272 can optionally furtherinclude sending the result data to another uplink processing virtualizedfunction of the virtual cell.

In Example 274, the subject matter of Example 272 can optionally includewherein the other uplink processing virtualized function is running atanother terminal device of the virtual cell.

In Example 275, the subject matter of Example 272 can optionally furtherinclude wirelessly transmitting the result data to a radio accessnetwork over a backhaul link.

In Example 276, the subject matter of any one of Examples 267 to 275 canoptionally include wherein the virtualized function is also allocated toa resource platform of another terminal device of the virtual cell, andwherein performing the virtualized function includes performing thevirtualized function in cooperation with the resource platform of theother terminal device.

In Example 277, the subject matter of any one of Examples 267 to 276 canoptionally include wherein the resource platform includes computeresources, storage resources, or network resources that are logicallydesignated as part of a resource pool for the virtual cell.

In Example 278, the subject matter of any one of Examples 267 to 277 canoptionally include wherein receiving the allocation includes wirelesslyreceiving the allocation via a baseband modem of the terminal device.

Example 279 is a method of operating a terminal device, the methodincluding receiving an allocation of a virtualized function from avirtual cell, configuring a resource platform of the terminal devicewith software for performing the virtualized function, performing thevirtualized function in cooperation with a resource platform of anotherterminal device of the virtual cell.

Example 280 is a method of operating a terminal device, the methodincluding executing a virtualized function manager for a virtual cell,identifying a virtualized function that uses resources platforms ofmultiple terminal devices of the virtual cell, identifying a pluralityof terminal devices of the virtual cell based on wireless links betweenthe plurality of terminal devices, and allocating the virtualizedfunction to the plurality of terminal devices for execution in adistributed manner.

In Example 281, the subject matter of Example 280 can optionally includewherein the virtualized function is configured to distributed executionat resource platforms of multiple terminal devices, or is configured touse result data from a counterpart virtualized function executable onanother terminal device.

In Example 281, the subject matter of Example 280 or 281 can optionallyinclude wherein identifying the plurality of terminal devices includesevaluating radio measurements that characterize the wireless linksbetween the plurality of terminal devices, and identifying the pluralityof terminal devices based on a strength of the radio measurements.

In Example 283, the subject matter of Example 280 or 281 can optionallyinclude wherein identifying the plurality of terminal devices includesevaluating positions of the plurality of terminal devices, andidentifying the plurality of terminal devices based on a relativeproximity indicated by their positions.

In Example 284, the subject matter of any one of Examples 280 to 283 canoptionally include wherein identifying the plurality of terminal devicesincludes determining a number of terminal devices that the virtualizedfunction, and selecting a plurality of terminal devices of the virtualcell equal in quantity to the number as the plurality of terminaldevices.

In Example 285, the subject matter of any one of Examples 280 to 284 canoptionally include wherein allocating the virtualized function to theplurality of terminal devices includes wirelessly transmitting anallocation of the virtualized function to the plurality of terminaldevices via a baseband modem of the terminal device.

Example 286 is a method of operating a terminal device, the methodincluding communicating with terminal devices of a virtual cell,executing a master terminal device virtualized function for the virtualcell in cooperation with a resource platform of another terminal deviceof the virtual cell, identifying a virtualized function that usesresource platforms of multiple terminal devices of the virtual cell,identifying a plurality of terminal devices of the virtual cell based onwireless links between the plurality of terminal devices, and allocatingthe virtualized function to the plurality of terminal devices forexecution in a distributed manner.

Example 287 is a method of operating terminal device, the methodincluding executing a virtualized function manager for a virtualnetwork, identifying a virtualized function that uses resource platformsof multiple terminal devices of the virtual network, identifying aplurality of terminal devices of the virtual network based on wirelesslinks between the plurality of terminal devices, and allocating thevirtualized function to the plurality of terminal devices for executionin a distributed manner.

Example 288 is a method of operating a terminal device, the methodincluding communicating with terminal devices of a virtual network,executing a master terminal device virtualized function for the virtualnetwork in cooperation with a resource platform of another terminaldevice of the virtual network, identifying a virtualized function thatuses resource platforms of multiple terminal devices of the virtualnetwork, identifying a plurality of terminal devices of the virtualnetwork based on wireless links between the plurality of terminaldevices, and allocating the virtualized function to the plurality ofterminal devices for execution in a distributed manner.

Example 289 is a method of operating a terminal device, the methodincluding executing a virtualized function manager for a virtual cell,identifying, for each of a plurality of virtualized functions, one ormore terminal devices of the virtual cell, and allocating each of theplurality of virtualized functions to the corresponding one or moreterminal devices.

Example 290 is a method of operating a terminal device, the methodincluding exchanging signaling with one or more terminal devices to joina virtual network, receiving an allocation for a virtualized functionfrom a virtualized function manager of the virtual network, andvirtually performing the virtualized function in cooperation with aresource platform of another terminal device of the virtual network.

Example 291 is a method of operating a virtual cell, the methodincluding allocating a plurality of virtualized functions between aplurality of terminal devices, performing the respectively allocatedvirtualized functions at the plurality of terminal devices, andproviding radio access to one or more served terminal devices viaexecution of the virtualized functions.

Example 292 is a non-transitory computer readable medium storinginstructions that when executed by a processor causes the processor toperform the method of any one of Examples 261 to 291.

Example 293 is a device including a processor, and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 261 to 291.

Example 294 is a terminal device including means for receiving anallocation of a virtualized function from a virtual cell, means forconfiguring a resource platform of the terminal device for thevirtualized function, means for performing the virtualized function withthe resource platform to obtain result data, and means for sending theresult data to another terminal device of the virtual cell.

Example 295 is a terminal device including means for receiving anallocation of a virtualized function from a virtual cell, means forconfiguring a resource platform of the terminal device for thevirtualized function, and means for performing the virtualized functionto provide a cell processing function or a radio activity function for aterminal device served by the virtual cell.

Example 296 is a terminal device including means for receiving anallocation of a virtualized function from a virtual cell, means forconfiguring a resource platform of the terminal device with for thevirtualized function, and means for performing the virtualized functionin cooperation with a resource platform of another terminal device ofthe virtual cell.

Example 297 is a terminal device including means for executing avirtualized function manager for a virtual cell, means for identifying avirtualized function that uses resources platforms of multiple terminaldevices of the virtual cell, means for identifying a plurality ofterminal devices of the virtual cell based on wireless links between theplurality of terminal devices, and means for allocating the virtualizedfunction to the plurality of terminal devices for execution in adistributed manner.

Example 298 is a terminal device including means for communicating withterminal devices of a virtual cell, means for executing a masterterminal device virtualized function for the virtual cell in cooperationwith a resource platform of another terminal device of the virtual cell,means for identifying a virtualized function that uses resourceplatforms of multiple terminal devices of the virtual cell, means foridentifying a plurality of terminal devices of the virtual cell based onwireless links between the plurality of terminal devices, and means forallocating the virtualized function to the plurality of terminal devicesfor execution in a distributed manner.

Example 299 is a terminal device including means for executing avirtualized function manager for a virtual network, means foridentifying a virtualized function that uses resource platforms ofmultiple terminal devices of the virtual network, means for identifyinga plurality of terminal devices of the virtual network based on wirelesslinks between the plurality of terminal devices, and means forallocating the virtualized function to the plurality of terminal devicesfor execution in a distributed manner.

Example 300 is a terminal device including means for communicating withterminal devices of a virtual network, means for executing a masterterminal device virtualized function for the virtual network incooperation with a resource platform of another terminal device of thevirtual network, means for identifying a virtualized function that usesresource platforms of multiple terminal devices of the virtual network,means for identifying a plurality of terminal devices of the virtualnetwork based on wireless links between the plurality of terminaldevices, and means for allocating the virtualized function to theplurality of terminal devices for execution in a distributed manner.

Example 301 is a terminal device including means for executing avirtualized function manager for a virtual cell, means for identifying,for each of a plurality of virtualized functions, one or more terminaldevices of the virtual cell, and means for allocating each of theplurality of virtualized functions to the corresponding one or moreterminal devices.

Example 302 is a terminal device including means for exchangingsignaling with one or more terminal devices to join a virtual network,means for receiving an allocation for a virtualized function from avirtualized function manager of the virtual network, and means forvirtually performing the virtualized function in cooperation with aresource platform of another terminal device of the virtual network.

Example 303 is a communication device including a function controllerconfigured to determine that a triggering condition for creating avirtual cell is met, and to define a geographic region for the virtualcell, and a baseband modem configured to transmit a discovery signal toinvite nearby terminal devices to join the virtual cell if thetriggering condition is met, the function controller further configuredto determine whether to accept one or more responding terminal devicesinto the virtual cell based on whether the one or more respondingterminal devices are in the geographic region.

In Example 304, the subject matter of Example 303 can optionally furtherinclude one or more antennas and a radio frequency (RF) transceiver,wherein the baseband modem is configured to wirelessly transmit thediscovery signal via the RF transceiver and the one or more antennas.

In Example 305, the subject matter of Example 303 or 304 can optionallyinclude wherein the function controller is configured to determine thatthe triggering conditions is met by determining that a network loadexceeds a threshold, or determining that an area has poor radio accesscoverage.

In Example 306, the subject matter of any one of Examples 303 to 305 canoptionally include wherein the geographic region is a fixed area or apredefined area.

In Example 307, the subject matter of any one of Examples 303 to 305 canoptionally include wherein the geographic region is a dynamic area thatchanges over time.

In Example 308, the subject matter of any one of Examples 303 to 307 canoptionally include wherein the baseband modem is further configured to,after transmitting the discovery signal, receive discovery responsesignals from the one or more responding terminal devices.

In Example 309, the subject matter of Example 308 can optionally includewherein the discovery response signals include a current position of theone or more responding terminal devices, and wherein the functioncontroller is configured to determine whether the one or more respondingterminal devices are within the geographic region based on the currentpositions.

In Example 310, the subject matter of Example 309 can optionally includewherein the function controller is configured to accept into the virtualcell those of the one or more responding terminal devices that providecurrent positions within the geographic region.

In Example 311, the subject matter of Example 308 can optionally includewherein receipt of the discovery response signals indicates that the oneor more responding terminal devices are within the geographic region,and wherein the function controller is configured to accept the one ormore responding terminal devices into the virtual cell.

In Example 312, the subject matter of any one of Examples 303 to 311 canoptionally include wherein the function controller is further configuredto, after the virtual cell is created, allocate one or more virtual cellvirtualized functions to the one or more responding terminal devices.

In Example 313, the subject matter of any one of Examples 303 to 311 canoptionally include wherein the function controller is configured toreceive an allocation of a virtual cell virtualized function from avirtualized function manager of the virtual cell, the communicationdevice further including a resource platform configured to execute thevirtual cell virtualized function to provide cell functionality of thevirtual cell.

Example 314 is a communication device including a function controllerconfigured to determine a current position of a first terminal device ofa virtual cell, and to determine whether the current position of thefirst terminal device is within a geographic region for the virtualcell, and a baseband modem configured to, if the current position of thefirst terminal device outside of the geographic region, transmit exitsignaling to the first terminal device for the first terminal device toexit the virtual cell.

In Example 315, the subject matter of Example 314 can optionally furtherinclude one or more antennas and a radio frequency (RF) transceiver,wherein the baseband modem is configured to wirelessly transmit the exitsignaling via the RF transceiver and the one or more antennas.

In Example 316, the subject matter of Example 314 or 315 can optionallyinclude wherein the function controller is configured to re-allocate avirtual cell virtualized function, that was previously allocated to thefirst terminal device, to a second terminal device of the virtual cell.

In Example 317, the subject matter of any one of Examples 314 to 316 canoptionally include wherein the function controller is configured todetermine the current position of the first terminal device by receivinga position report from the first terminal device that indicates thecurrent position of the first terminal device.

In Example 318, the subject matter of any one of Examples 314 to 317 canoptionally include wherein the function controller is configured tolocally store region data that defines boundaries of the geographicregion, and to determine whether the first terminal device is in thegeographic region by evaluating the region data and the currentposition.

Example 319 is a communication device including one or more processorsconfigured to determine current positions of a plurality of terminaldevices that form a virtual cell, wherein the virtual cell includes acoverage area divided into multiple subareas, select a first terminaldevice of the plurality of terminal devices to assign to a first subareaof the multiple subareas, and allocate, to the first terminal device, afirst virtual cell virtualized function for providing cell functionalityto served terminal devices of the virtual cell in the first subarea.

In Example 320, the subject matter of Example 319 can optionally furtherinclude one or more antennas, a radio frequency (RF) transceiver, and abaseband modem, wherein the one or more processors are configured toallocate the first virtual cell virtualized function to the firstterminal device by wirelessly transmitting signaling to the firstterminal device that allocates the first virtual cell virtualizedfunction the first terminal device.

In Example 321, the subject matter of Example 319 or 320 can optionallyinclude wherein the one or more processors are configured to determinethe current positions of the plurality of terminal devices by receivingposition reports from the plurality of terminal devices that indicatetheir respective current positions.

In Example 322, the subject matter of any one of Examples 319 to 321 canoptionally include wherein the one or more processors are furtherconfigured to logically divide the coverage area into the multiplesubareas based on the current positions of the plurality of terminaldevices.

In Example 323, the subject matter of any one of Examples 319 to 321 canoptionally include wherein the one or more processors are configured toselect the first terminal device by determining, based on its currentposition, that the first terminal device is in the first subarea.

In Example 324, the subject matter of any one of Examples 319 to 323 canoptionally include wherein the one or more processors are configured toallocate a plurality of virtual cell virtualized functions, includingthe first virtual cell virtualized function, to the first terminaldevice that relate to radio activity, lower-layer cell processing, andupper-layer cell processing for served terminal devices in the firstsubarea.

In Example 325, the subject matter of any one of Examples 319 to 323 canoptionally include wherein the first virtual cell virtualized functionrelates to radio activity or lower-layer cell processing.

In Example 326, the subject matter of any one of Examples 319 to 323 canoptionally include wherein the one or more processors are configured toselect a second terminal device of the plurality of terminal devices toassign to a second subarea of the multiple subareas, and to allocate, tothe second terminal device, a second virtual cell virtualized functionfor providing cell functionality to served terminal devices of thevirtual cell in the second subarea.

In Example 327, the subject matter of any one of Examples 319 to 323 canoptionally include wherein the one or more processors are furtherconfigured to select a second terminal device of the plurality ofterminal devices to assign to the first subarea, and to allocate, to thesecond terminal device, a second virtual cell virtualized function forproviding other cell functionality to served terminal devices of thevirtual cell in the first subarea.

In Example 328, the subject matter of Example 327 can optionally includewherein the first virtual cell virtualized function relates to radioactivity or lower-layer cell processing, and the second virtual cellvirtualized function relates to upper-layer cell processing.

Example 329 is a communication device including a function controllerconfigured to receive an allocation of a virtual cell virtualizedfunction for providing cell functionality to served terminal devices ina first subarea of a virtual cell, and a resource platform configured toexecute the virtual cell virtualized function to provide the cellfunctionality to the served terminal devices in the first subarea.

In Example 330, the subject matter of Example 329 can optionally includewherein a coverage area of the virtual cell is logically divided into aplurality of subareas including the first subarea.

In Example 331, the subject matter of Example 329 or 330 can optionallyinclude wherein the resource platform includes one or more processorsfor computing functionality, a memory for storage functionality, orwireless communication components for network functionality.

In Example 332, the subject matter of any one of Examples 329 to 331 canoptionally include wherein the virtual cell virtualized functionincludes software that defines radio activity or cell processing for thevirtual cell, wherein the resource platform is configured to execute thesoftware.

In Example 333, the subject matter of any one of Examples 329 to 332 canoptionally include wherein the virtual cell virtualized function definesradio activity for the virtual cell, and wherein the resource platformis configured to perform transmissions to served terminal devices in thefirst subarea or to receive transmissions from served terminal devicesin the first subarea when executing the virtual cell virtualizedfunction.

In Example 334, the subject matter of any one of Examples 329 to 332 canoptionally include wherein the function controller is further configuredto receive an allocation of one or more virtual cell virtualizedfunctions and the resource platform is configured to execute the one ormore virtual cell virtualized functions to provide other cellfunctionality to served terminal devices in the first subarea.

In Example 335, the subject matter of Example 334 can optionally includewherein cell functionality of the virtual cell virtualized function andthe one or more virtual cell virtualized functions includes radioactivity, lower-layer cell processing, and upper-layer cell processing.

In Example 336, the subject matter of any one of Examples 329 to 335 canoptionally include wherein one or more processors of the resourceplatform are configured to determine that a served terminal device hasmoved from the first subarea to a second subarea to which anothercommunication device of the virtual cell is assigned, and transfer cellfunctionality for the first terminal device from the communicationdevice to the other communication device.

Example 337 is a communication device including one or more processorsconfigured to identify a plurality of virtual cell virtualized functionsincluding one or more first virtual cell virtualized functions of afirst type and one or more second virtual cell virtualized functions ofa second type, select, from the plurality of virtual cell virtualizedfunctions, a selected virtual cell virtualized function of the first orsecond type based on an expected duration of time for a terminal deviceto remain in a virtual cell, and allocate the selected virtual cellvirtualized function to the terminal device.

In Example 338, the subject matter of Example 337 can optionally furtherinclude one or more antennas, a radio frequency (RF) transceiver, and abaseband modem, where the one or more processors are configured toallocate the selected virtual cell virtualized function to the terminaldevice by wirelessly transmitting signaling to the terminal device thatallocates the selected virtual cell virtualized function to the terminaldevice.

In Example 339, the subject matter of Example 337 or 338 can optionallyinclude wherein the one or more processors are configured to receivesignaling from the terminal device that indicates the expected duration.

In Example 340, the subject matter of any one of Examples 337 to 339 canoptionally include wherein the one or more first virtual cellvirtualized functions provide basic functionality of the virtual celland the one or more second virtual cell virtualized functions provideauxiliary functionality of the virtual cell.

In Example 341, the subject matter of Example 340 can optionally includewherein the one or more processors are weighted towards selecting aselected virtual cell virtualized function of the first type for longerexpected durations, and weighted towards selecting a selected virtualcell virtualized function of the second type for shorter expecteddurations.

Example 342 is a communication device including one or more processorsconfigured to identify a plurality of virtual cell virtualized functionsincluding one or more first virtual cell virtualized functions of afirst type and one or more second virtual cell virtualized functions ofa second type, select, from the plurality of virtual cell virtualizedfunctions, a selected virtual cell virtualized function of the first orsecond type based on a duration of time a terminal device has been partof a virtual cell, and allocate the selected virtual cell virtualizedfunction to the terminal device.

In Example 343, the subject matter of Example 342 can optionally includewherein the one or more processors are configured to use a timestampspecifying when the terminal device joined the virtual cell to determinethe duration of time that the terminal device has been part of thevirtual cell.

In Example 344, the subject matter of Example 342 or 343 can optionallyinclude wherein the one or more processors are configured to rank aplurality of terminal devices, including the terminal device, based onthe durations of time that the plurality of terminal devices have beenpart of the virtual cell, and to allocate the plurality of virtual cellvirtualized functions to the plurality of terminal devices based on theranking.

In Example 345, the subject matter of Example 344 can optionally includewherein the ranking is from highest durations of time to lowest and theone or more first virtual cell virtualized functions provide basicfunctionality of the virtual cell and the one or more second virtualcell virtualized functions provide auxiliary functionality of thevirtual cell, and wherein the one or more processors are configured toallocate the one or more first virtualized functions to higher-rankedterminal devices in the ranking and to allocate the one or more secondvirtualized functions to lower-ranked terminal devices in the ranking.

Example 346 is a method of operating a communication device, the methodincluding determining that a triggering condition for creating a virtualcell is met, defining a geographic region for the virtual cell,transmitting a discovery signal to invite nearby terminal devices tojoin the virtual cell if the triggering condition is met, anddetermining whether to accept one or more responding terminal devicesinto the virtual cell based on whether the one or more respondingterminal devices are in the geographic region.

In Example 347, the subject matter of Example 346 can optionally includewherein transmitting the discovery signal includes wirelesslytransmitting the discovery signal via an RF transceiver and one or moreantennas.

In Example 348, the subject matter of Example 346 or 347 can optionallyinclude wherein determining that the triggering condition is metincludes determining that a network load is above a threshold, ordetermining that a radio coverage level is below a threshold.

In Example 349, the subject matter of any one of Examples 346 to 348 canoptionally include wherein the geographic region is a fixed area or apredefined area.

In Example 350, the subject matter of any one of Examples 346 to 348 canoptionally include wherein the geographic region is a dynamic area thatchanges over time.

In Example 351, the subject matter of any one of Examples 346 to 350 canoptionally further include after transmitting the discovery signal,receiving discovery response signals from the one or more respondingterminal devices.

In Example 352, the subject matter of Example 351 can optionally includewherein the discovery response signals include a current position of theone or more responding terminal devices, and wherein determining whetherthe one or more responding terminal devices are within the geographicregion includes determining whether the one or more responding terminaldevices are within the geographic region based on the current positions.

In Example 353, the subject matter of Example 352 can optionally furtherinclude accepting into the virtual cell those of the one or moreresponding terminal devices that provide current positions within thegeographic region.

In Example 354, the subject matter of Example 351 can optionally includewherein receipt of the discovery response signals indicates that the oneor more responding terminal devices are within the geographic region,the method further including accepting the one or more respondingterminal devices into the virtual cell.

In Example 355, the subject matter of any one of Examples 346 to 354 canoptionally further include after the virtual cell is created, allocatingone or more virtual cell virtualized functions to the one or moreresponding terminal devices.

In Example 356, the subject matter of any one of Examples 346 to 354 canoptionally further include receiving an allocation of a virtual cellvirtualized function from a master terminal device of the virtual cell,and executing the virtual cell virtualized function to provide cellfunctionality to one or more served terminal devices of the virtualcell.

Example 357 is a method of operating a communication device, the methodincluding determining a current position of a first terminal device of avirtual cell, determining whether the current position of the firstterminal device is within a geographic region for the virtual cell, andafter determining that the current position of the first terminal deviceis outside of the geographic region, transmitting exit signaling to thefirst terminal device for the first terminal device to exit the virtualcell.

In Example 358, the subject matter of Example 357 can optionally includewherein transmitting the exit signaling to the first terminal deviceincludes wirelessly transmitting the exit signaling via a radiofrequency (RF) transceiver and one or more antennas of the communicationdevice.

In Example 359, the subject matter of Example 357 or 358 can optionallyfurther include after transmitting the exit signaling, re-allocating avirtual cell virtualized function to a second terminal device of thevirtual cell, where the virtual cell virtualized function was previouslyallocated to the first terminal device.

In Example 360, the subject matter of any one of Examples 357 to 359 canoptionally include wherein determining the current position of the firstterminal device includes receiving a position report from the firstterminal device that indicates the current position of the firstterminal device.

In Example 361, the subject matter of any one of Examples 357 to 360 canoptionally include wherein determining whether the first terminal deviceis outside of the geographic region includes evaluating stored regiondata defining boundaries of the geographic area and the current positionto determine whether the current position is within the boundaries ofthe geographic area.

Example 362 is a method of operating a communication device, the methodincluding determining current positions of a plurality of terminaldevices that form a virtual cell, wherein the virtual cell includes acoverage area divided into multiple subareas, selecting a first terminaldevice of the plurality of terminal devices to assign to a first subareaof the multiple subareas, and allocating, to the first terminal device,a first virtual cell virtualized function for providing cellfunctionality to served terminal devices of the virtual cell in thefirst subarea.

In Example 363, the subject matter of Example 362 can optionally includewherein allocating the first virtual cell virtualized function to thefirst terminal device includes wirelessly transmitting signaling to thefirst terminal device that allocates the first virtual cell virtualizedfunction to the first terminal device.

In Example 364, the subject matter of Example 362 or 363 can optionallyinclude wherein determining the current positions of the plurality ofterminal devices includes receiving position reports from the pluralityof terminal devices that indicate their respective current positions.

In Example 365, the subject matter of any one of Examples 362 to 364 canoptionally further include logically dividing the coverage area into themultiple subareas based on the current positions of the plurality ofterminal devices.

In Example 366, the subject matter of any one of Examples 362 to 364 canoptionally include wherein selecting the first terminal device includesdetermining, based on the current position of the first terminal device,that the first terminal device is in the first subarea.

In Example 367, the subject matter of any one of Examples 362 to 366 canoptionally further include allocating a plurality of virtual cellvirtualized functions, including the first virtual cell virtualizedfunction, to the first terminal device that relate to radio activity,lower-layer cell processing, and upper-layer cell processing for servedterminal devices in the first subarea.

In Example 368, the subject matter of any one of Examples 362 to 366 canoptionally include wherein the first virtual cell virtualized functionrelates to radio activity or lower-layer cell processing.

In Example 369, the subject matter of any one of Examples 362 to 366 canoptionally further include selecting a second terminal device of theplurality of terminal devices to assign to a second subarea of themultiple subareas, and allocating, to the second terminal device, asecond virtual cell virtualized function for providing cellfunctionality to served terminal devices of the virtual cell in thesecond subarea.

In Example 370, the subject matter of any one of Examples 362 to 366 canoptionally further include selecting a second terminal device of theplurality of terminal devices to assign to the first subarea, andallocating, to the second terminal device, a second virtual cellvirtualized function for providing other cell functionality to servedterminal devices of the virtual cell in the first subarea.

In Example 371, the subject matter of Example 370 can optionally includewherein the first virtual cell virtualized function relates to radioactivity or lower-layer cell processing, and the second virtual cellvirtualized function relates to upper-layer cell processing.

Example 372 is a method of operating a communication device, the methodincluding receiving an allocation of a virtual cell virtualized functionfor providing cell functionality to served terminal devices in a firstsubarea of a virtual cell, and executing the virtual cell virtualizedfunction to provide the cell functionality to the served terminaldevices in the first subarea.

In Example 373, the subject matter of Example 372 can optionally includewherein a coverage area of the virtual cell is logically divided into aplurality of subareas including the first subarea.

In Example 374, the subject matter of Example 372 or 373 can optionallyinclude wherein executing the virtual cell virtualized function toprovide the cell functionality includes executing the virtual cellvirtualized function on a resource platform including one or moreprocessors for computing functionality, a memory for storagefunctionality, or wireless communication components for networkfunctionality.

In Example 375, the subject matter of any one of Examples 372 to 374 canoptionally include wherein the virtual cell virtualized functionincludes software that defines radio activity or cell processing for thevirtual cell, and wherein executing the virtual cell virtualizedfunction includes performing the radio activity or cell processing forthe virtual cell.

In Example 376, the subject matter of any one of Examples 372 to 375 canoptionally include wherein the virtual cell virtualized function definesradio activity for the virtual cell, and wherein executing the virtualcell virtualized function includes performing transmission to servedterminal devices in the first subarea or receiving transmission fromserved terminal devices in the first subarea.

In Example 377, the subject matter of any one of Examples 372 to 375 canoptionally further include receiving an allocation of one or morevirtual cell virtualized functions, and executing the one or morevirtual cell virtualized functions to provide other cell functionalityto served terminal devices in the first subarea.

In Example 378, the subject matter of Example 377 can optionally includewherein the cell functionality of the virtual cell virtualized functionand the one or more virtual cell virtualized functions includes radioactivity, lower-layer cell processing, and upper-layer cell processingfor served terminal devices in the first subarea.

In Example 379, the subject matter of any one of Examples 372 to 377 canoptionally further include determining that a served terminal device hasmoved from the first subarea to a second subarea to which anothercommunication device of the virtual cell is assigned, and transferringcell functionality for the first terminal device from the communicationdevice to the other communication device.

Example 380 is a method of operating a communication device, the methodincluding identifying a plurality of virtual cell virtualized functionsincluding one or more first virtual cell virtualized functions of afirst type and one or more second virtual cell virtualized functions ofa second type, selecting, from the plurality of virtual cell virtualizedfunctions, a selected virtual cell virtualized function of the first orsecond type based on an expected duration of time for a terminal deviceto remain in a virtual cell, and allocating the selected virtual cellvirtualized function to the terminal device.

In Example 381, the subject matter of Example 380 can optionally includewherein allocating the selected virtual cell virtualized function to theterminal device includes wirelessly transmitting signaling to theterminal device via one or more antennas, a radio frequency (RF)transceiver, and a baseband modem of the communication device.

In Example 382, the subject matter of Example 380 or 381 can optionallyfurther include receiving signaling from the terminal device thatindicates the expected duration.

In Example 383, the subject matter of any one of Examples 380 to 382 canoptionally include wherein the one or more first virtual cellvirtualized functions provide basic functionality of the virtual celland the one or more second virtual cell virtualized functions provideauxiliary functionality of the virtual cell.

In Example 384, the subject matter of Example 383 can optionally includewherein selecting the selected virtual cell virtualized function isweighted towards selecting a selected virtual cell virtualized functionof the first type for longer expected durations, and weighted towardsselecting a selected virtual cell virtualized function of the secondtype for shorter expected durations.

Example 385 is a method of operating a communication device, the methodincluding identifying a plurality of virtual cell virtualized functionsincluding one or more first virtual cell virtualized functions of afirst type and one or more second virtual cell virtualized functions ofa second type, selecting, from the plurality of virtual cell virtualizedfunctions, a selected virtual cell virtualized function of the first orsecond type based on a duration of time a terminal device has been partof a virtual cell, and allocating the selected virtual cell virtualizedfunction to the terminal device.

In Example 386, the subject matter of Example 385 can optionally furtherinclude determining the duration of time that the terminal device hasbeen part of the cell using a timestamp specifying when the terminaldevice joined the virtual cell.

In Example 387, the subject matter of Example 385 or 386 can optionallyfurther include ranking a plurality of terminal devices, including theterminal device, based on the durations of time that the plurality ofterminal devices have been part of the virtual cell, and allocating theplurality of virtual cell virtualized functions to the plurality ofterminal devices based on the ranking.

In Example 388, the subject matter of Example 387 can optionally includewherein the ranking is from highest durations of time to lowest and theone or more first virtual cell virtualized functions provide basicfunctionality of the virtual cell and the one or more second virtualcell virtualized functions provide auxiliary functionality of thevirtual cell, the method further including allocating the one or morefirst virtualized functions to higher-ranked terminal devices in theranking and allocating the one or more second virtualized functions tolower-ranked terminal devices in the ranking.

Example 389 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 346 to388.

Example 390 is a device including one or more processors, and a memoryincluding instructions that when executed by the one or more processorscause the one or more processors to perform the method of any one ofExamples 346 to 388.

Example 391 is a communication device including means for determiningthat a triggering condition for creating a virtual cell is met, and todefine a geographic region for the virtual cell, means for transmittinga discovery signal to invite nearby terminal devices to join the virtualcell if the triggering condition being met, and means for determiningwhether to accept one or more responding terminal devices into thevirtual cell based on whether the one or more responding terminaldevices are in the geographic region.

Example 392 is a communication device including means for determining acurrent position of a first terminal device of a virtual cell, means fordetermining whether the current position of the first terminal device iswithin a geographic region for the virtual cell, and means fortransmitting exit signaling to the first terminal device for the firstterminal device to exit the virtual cell if the current position of thefirst terminal device outside of the geographic region.

Example 393 is a communication device including means for determiningcurrent positions of a plurality of terminal devices that form a virtualcell, wherein the virtual cell includes a coverage area divided intomultiple subareas, means for selecting a first terminal device of theplurality of terminal devices to assign to a first subarea of themultiple subareas, and means for allocating, to the first terminaldevice, a first virtual cell virtualized function for providing cellfunctionality to served terminal devices of the virtual cell in thefirst subarea.

Example 394 is a communication device including means for receiving anallocation of a virtual cell virtualized function for providing cellfunctionality to served terminal devices in a first subarea of a virtualcell, and means for executing the virtual cell virtualized function toprovide the cell functionality to the served terminal devices in thefirst subarea.

Example 395 is a communication device including means for identifying aplurality of virtual cell virtualized functions including one or morefirst virtual cell virtualized functions of a first type and one or moresecond virtual cell virtualized functions of a second type, means forselecting, from the plurality of virtual cell virtualized functions, aselected virtual cell virtualized function of the first or second typebased on an expected duration of time for a terminal device to remain ina virtual cell, and means for allocating the selected virtual cellvirtualized function to the terminal device.

Example 396 is a communication device including means for identifying aplurality of virtual cell virtualized functions including one or morefirst virtual cell virtualized functions of a first type and one or moresecond virtual cell virtualized functions of a second type, means forselecting, from the plurality of virtual cell virtualized functions, aselected virtual cell virtualized function of the first or second typebased on a duration of time a terminal device has been part of a virtualcell, and means for allocating the selected virtual cell virtualizedfunction to the terminal device.

Example 397 is a method for performing processing at a local server, themethod including receiving signaling from a cloud server that specifiesa processing function assigned for processing offload by the localserver, receiving, from a traffic filter, target data that originatesfrom a local network, applying the processing function to the targetdata to obtain processed data, and sending the processed data to thecloud server for cloud processing.

In Example 398, the subject matter of Example 397 can optionally includewherein the signaling includes software for the processing function, themethod further including loading the software into a processing platformfor execution.

In Example 399, the subject matter of Example 397 can optionally includewherein the signaling includes an identifier that identifies theprocessing function from a plurality of processing functions, the methodfurther including retrieving software for the processing function from amemory and loading the software into a processing platform forexecution.

In Example 400, the subject matter of any one of Examples 397 to 399 canoptionally further include receiving further processed data from thecloud server, and applying an additional processing function on thefurther processed data.

In Example 401, the subject matter of Example 400 can optionally includewherein the processing function, the cloud processing, and theadditional processing function each constitute part of an overallscheduled processing for the target data.

In Example 402, the subject matter of any one of Examples 397 to 401 canoptionally further include receiving an updated processing function fromthe cloud server, receiving additional target data from the trafficfilter, applying the updated processing function to the additionaltarget data to obtain additional processed data, and sending theprocessed data to the cloud server for additional cloud processing.

In Example 403, the subject matter of any one of Examples 397 to 402 canoptionally include wherein the target data is filtered raw dataoriginating from the local network.

In Example 404, the subject matter of any one of Examples 397 to 403 canoptionally include wherein the target data is filtered raw datagenerated by one or more terminal devices from the local network.

In Example 405, the subject matter of any one of Examples 397 to 404 canoptionally include wherein the target data is sensing data oroperational data generated by one or more terminal devices from thelocal network.

In Example 406, the subject matter of any one of Examples 397 to 405 canoptionally include wherein the processing function includes part of anoverall scheduled processing for the target data, and wherein the cloudprocessing includes a remaining part of the overall scheduled processingfor the target data.

In Example 407, the subject matter of Example 406 can optionally includewherein the cloud processing is the remainder of the overall scheduledprocessing for the target data.

In Example 408, the subject matter of any one of Examples 397 to 407 canoptionally further include sending the processed data to the localnetwork.

Example 409 is a method for performing processing functions at a localserver, the method including selecting a processing function forprocessing offload, receiving, from a traffic filter, target data thatoriginates from a local network, applying the processing function to thetarget data to obtain processed data, and sending the processed data tothe cloud server for cloud processing.

In Example 410, the subject matter of Example 409 can optionally furtherinclude selecting a filter template that identifies the target data, andsending the filter template to the traffic filter.

In Example 411, the subject matter of Example 410 can optionally includewherein the target data is raw data that matches the filter template.

In Example 412, the subject matter of Example 410 or 411 can optionallyinclude wherein selecting the filter template includes selecting one ormore parameters that define the target data.

In Example 413, the subject matter of any one of Examples 409 to 412 canoptionally further include selecting an updated processing functionbased on one or more dynamic parameters of the processing offload,applying the updated processing function to additional target data toobtain additional processed data, and sending the additional processeddata to the cloud server for cloud processing.

In Example 414, the subject matter of Example 413 can optionally furtherinclude selecting an updated filter template based on the one or moredynamic parameters, sending the updated filter template to the trafficfilter, wherein the additional target data matches the filter template.

The method of any one of Examples 409 to 414, further including sendingthe processed data to the local network.

In Example 416, the subject matter of any one of Examples 409 to 415 canoptionally include wherein selecting the processing function includesselecting the processing function from a plurality of preinstalledprocessing functions stored on a processing function memory, the methodfurther including to loading software for the processing function fromthe processing function memory into the one or more processors.

Example 417 is a method for performing processing functions at a localserver, the method including receiving signaling from a cloud serverthat specifies a processing function assigned for processing offload bythe local server, receiving, from a traffic filter, target data thatoriginates from a local network, applying the processing function to thetarget data to obtain processed data, and sending the processed data tothe local network.

Example 418 is a method for performing processing functions at a localserver, the method including selecting a processing function forprocessing offload, receiving, from a traffic filter, target data thatoriginates from a local network, applying the processing function to thetarget data to obtain processed data, and sending the processed data tothe local network.

Example 419 is a local server including a controller configured toreceive signaling from a cloud server that specifies a processingfunction assigned for processing offload by the local server, and toreceive target data from a traffic filter that originates from a localnetwork, a processing platform including one or more processors andconfigured to apply the processing function to the target data to obtainprocessed data, the controller configured to send the processed data tothe cloud server for cloud processing.

In Example 420, the subject matter of Example 419 can optionally includewherein the signaling includes software for the processing function, theprocessing platform configured to load the software into the one or moreprocessors.

In Example 421, the subject matter of Example 419 can optionally furtherinclude a processing function memory configured to store a plurality ofpreinstalled processing functions, wherein the signaling includes anidentifier that identifies the processing function from the plurality ofpreinstalled processing functions and the processing platform isconfigured to load the software from the processing function memory intothe one or more processors.

In Example 422, the subject matter of any one of Examples 419 to 421 canoptionally include wherein the controller is configured to receivefurther processed data from the cloud server, and wherein the processingplatform is configured to apply an additional processing function on thefurther processed data.

In Example 423, the subject matter of Example 422 can optionally includewherein the processing function, the cloud processing, and theadditional processing function each constitute part of an overallscheduled processing for the target data.

In Example 424, the subject matter of any one of Examples 419 to 423 canoptionally include wherein the controller is further configured toreceive an updated processing function from the cloud server and toreceive additional target data from the traffic filter, wherein theprocessing platform is further configured to apply the updatedprocessing function to the additional target data to obtain additionalprocessed data, and wherein the controller is further configured to sendthe processed data to the cloud server for additional cloud processing.

In Example 425, the subject matter of any one of Examples 419 to 424 canoptionally include wherein the target data is filtered raw dataoriginating from the local network.

In Example 426, the subject matter of any one of Examples 419 to 425 canoptionally include wherein the target data is sensing data oroperational data originating at one or more terminal devices from thelocal network.

In Example 427, the subject matter of any one of Examples 419 to 426 canoptionally include wherein the processing function includes part of anoverall scheduled processing for the target data, and wherein the cloudprocessing includes a remaining part of the overall scheduled processingfor the target data.

In Example 428, the subject matter of Example 427 can optionally includewherein the cloud processing is the remainder of the overall scheduledprocessing for the target data.

In Example 429, the subject matter of any one of Examples 419 to 428 canoptionally include wherein the controller is further configured to sendthe processed data to the local network.

Example 430 is a local server including a controller configured toselect a processing function for processing offload, and to receive,from a traffic filter, target data that originates from a local network,and a processing platform including one or more processors andconfigured to apply the processing function to the target data to obtainprocessed data, the controller further configured to send the processeddata to the cloud server for cloud processing.

In Example 431, the subject matter of Example 430 can optionally includewherein the controller is further configured to select a filter templatethat identifies the target data, and to send the filter template to thetraffic filter.

In Example 432, the subject matter of Example 431 can optionally includewherein the target data is raw data that matches the filter template.

In Example 433, the subject matter of Example 431 or 432 can optionallyinclude wherein the controller is configured to select the filtertemplate by selecting one or more parameters that define the targetdata.

In Example 434, the subject matter of any one of Examples 430 to 433 canoptionally include wherein the controller is further configured toselect an updated processing function based on one or more dynamicparameters of the processing offload, wherein the processing platform isfurther configured to apply the updated processing function toadditional target data to obtain additional processed data, and whereinthe controller is further configured to send the additional processeddata to the cloud server for cloud processing.

In Example 435, the subject matter of any one of Examples the controlleris can optionally be configured to select an updated filter templatebased on the one or more dynamic parameters, and to send the updatedfilter template to the traffic filter, wherein the additional targetdata matches the filter template.

In Example 436, the subject matter of any one of Examples 430 to 435 canoptionally include wherein the controller is further configured to sendthe processed data to the local network.

In Example 437, the subject matter of any one of Examples 430 to 436 canoptionally include wherein the controller is configured to select theprocessing function from a plurality of preinstalled processingfunctions stored on a processing function memory, and wherein theprocessing platform is configured to load software for the processingfunction from the processing function memory into the one or moreprocessors.

Example 438 is a local server including a controller configured toreceive signaling from a cloud server that specifies a processingfunction assigned for processing offload by the local server, and toreceive, from a traffic filter, target data that originates from a localnetwork, and a processing platform including one or more processors andconfigured to apply the processing function to the target data to obtainprocessed data, the controller further configured to send the processeddata to the local network.

Example 439 is a local server including a controller configured toselect a processing function for processing offload, and to receive,from a traffic filter, target data that originates from a local network,and a processing platform including one or more processors andconfigured to apply the processing function to the target data to obtainprocessed data, the controller further configured to send the processeddata to the local network.

Example 440 is a device including a template memory configured to storea filter template that defines one or more parameters of target data, atraffic filter configured to apply the filter template to raw dataoriginating from a local network, to identify target data from the rawdata based on the one or more parameters, and to route the target datato a local server for processing offload.

In Example 441, the subject matter of Example 440 can optionally furtherinclude an antenna, a radio transceiver, and a baseband system, andconfigured as a network access node of the local network.

In Example 442, the subject matter of Example 441 can optionally includewherein the network access node is a small cell.

In Example 443, the subject matter of Example 440 can optionally furtherinclude a router and configured as a server.

In Example 444, the subject matter of Example 440 can optionally furtherinclude an antenna, a radio transceiver, and a baseband modem, andconfigured as a terminal device.

In Example 445, the subject matter of Example 440 can optionally beconfigured as an integrated circuitry component for a terminal device, anetwork access node, or a server.

In Example 446, the subject matter of any one of Examples 440 to 445 canoptionally include wherein the raw data is user plane data originatingfrom one or more terminal devices of the local network.

In Example 447, the subject matter of any one of Examples 441 to 446 canoptionally include wherein the raw data is sensing or operational datagenerated by one or more terminal devices of the local network.

In Example 448, the subject matter of any one of Examples 440 to 447 canoptionally include wherein the traffic filter is configured to receivesignaling from a server that specifies the filter template.

In Example 449, the subject matter of Example 448 can optionally includewherein the signaling includes the one or more parameters of the filtertemplate and the template memory is configured to store the one or moreparameters of the filter template.

In Example 450, the subject matter of Example 448 can optionally includewherein the signaling identifies the filter template from a plurality offilter templates stored in the template memory

In Example 451, the subject matter of any one of Examples 448 to 450 canoptionally include wherein the server is the local server or a cloudserver.

In Example 452, the subject matter of any one of Examples 440 to 451 canoptionally include wherein the traffic filter is configured to apply thefilter template to the raw data and identify the target data from theraw data by performing packet inspection on packets of the raw data toidentify one or more characteristics of the packets, and determiningwhether the one or more characteristics of the packets match the one ormore parameters of the filter template, and classifying packets havingone or more characteristics that match the one or more parameters astarget data.

In Example 453, the subject matter of any one of Examples 440 to 452 canoptionally include wherein the one or more parameters of the filtertemplate identify a specific type of raw data, identify a specificgeographic area, or identify specific devices from which the raw dataoriginates.

In Example 454, the subject matter of any one of Examples 440 to 453 canoptionally include wherein the traffic filter is further configured toidentify the target data and other data from the raw data, and to routethe other data to a cloud server.

In Example 455, the subject matter of any one of Examples 440 to 454 canoptionally include wherein the template memory is configured to receiveand store an updated filter template that defines one or more updatedparameters of target data, and wherein the traffic filter is configuredto apply the updated filter template to additional raw data originatingfrom the local network, to identify additional target data from the rawdata based on the one or more updated parameters, and to route theadditional target data to the local server for processing offload.

Example 456 is a method for filtering and routing data, the methodincluding receiving signaling that specifies a filter template definingone or more parameters of target data, applying the filter template toraw data originating from a local network, identifying target data fromthe raw data based on the one or more parameters, and routing the targetdata to a local server for processing offload.

In Example 457, the subject matter of Example 456 can optionally includewherein the raw data is user plane data originating from one or moreterminal devices of the local network.

In Example 458, the subject matter of Example 456 or 457 can optionallyinclude wherein the raw data is sensing or operational data generated byone or more terminal devices of the local network.

In Example 459, the subject matter of any one of Examples 456 to 458 canoptionally include wherein receiving the signaling includes receivingthe signaling from a local server or a cloud server.

In Example 460, the subject matter of any one of Examples 456 to 459 canoptionally include wherein the signaling includes the one or moreparameters of the filter template, the method further including storingthe one or more parameters of the filter template in a template memory.

In Example 461, the subject matter of any one of Examples 456 to 459 canoptionally include wherein the signaling identifies the filter templatefrom a plurality of filter templates stored in the template memory.

In Example 462, the subject matter of any one of Examples 456 to 461 canoptionally include wherein applying the filter template to the raw dataand identifying the target data includes performing packet inspection onpackets of the raw data to identify one or more characteristics of thepackets, determining whether the one or more characteristics of thepackets match the one or more parameters of the filter template, andclassifying packets having one or more characteristics that match theone or more parameters as target data.

In Example 463, the subject matter of any one of Examples 456 to 462 canoptionally include wherein the one or more parameters of the filtertemplate identify a specific type of raw data, identify a specificgeographic area, or identify specific devices from which the raw dataoriginates.

In Example 464, the subject matter of any one of Examples 456 to 463 canoptionally further include identifying other data from the raw data, androuting the other data to a cloud server.

In Example 465, the subject matter of any one of Examples 456 to 464 canoptionally further include receiving signaling that specifies an updatedfilter template defining one or more updated parameters of target data,applying the update filter template to additional raw data originatingfrom the local network, identifying additional target data from the rawdata based on the one or more updated parameters, and routing theadditional target data to the local server for processing offload.

Example 466 is a method for execution at a cloud server, the methodincluding selecting a first processing function for processing offloadby a local server, and selecting a first filter template that definestarget data for the first processing function, sending signaling to thelocal server that specifies the first processing function, and sendingsignaling to a traffic filter that specifies the first filter template,selecting an updated processing function or an updated filter templatebased on one or more dynamic parameters of the processing offload, andsending signaling to the local server that specifies the updatedprocessing function or sending signaling to the traffic filter thatspecifies the updated filter template.

In Example 467, the subject matter of Example 466 can optionally furtherinclude monitoring a processing load of the local server, whereinselecting the updated processing function includes selecting the updatedprocessing function based on the processing load.

In Example 468, the subject matter of Example 467 can optionally includewherein selecting the updated processing function based on theprocessing load includes determining whether the processing load isabove a predefined threshold, and selecting the updated processingfunction to have a lower processing load than the first processingfunction if the processing load is above the threshold.

In Example 469, the subject matter of Example 466 can optionally furtherinclude monitoring a processing load of the cloud server, whereinselecting the updated processing function includes selecting the updatedprocessing function based on the processing load.

In Example 470, the subject matter of Example 469 can optionally includewherein selecting the updated processing function based on theprocessing load includes determining whether the processing load isabove a predefined threshold, and selecting the updated processingfunction to have a higher processing load than the first processingfunction if the processing load is above the threshold.

In Example 471, the subject matter of any one of Examples 466 to 470 canoptionally include wherein selecting the updated processing functionincludes selecting an updated processing function based on a cost oftransmitting data over a backhaul link, an amount of data beinggenerated at a local network that includes the local server, or a powerconsumption of the local server.

In Example 472, the subject matter of any one of Examples 466 to 471 canoptionally include wherein sending the signaling to the local serverthat specifies the first processing function includes sending signalingincluding software for the first processing function to the localserver.

In Example 473, the subject matter of any one of Examples 466 to 471 canoptionally include wherein sending the signaling to the local serverthat specifies the first processing function includes sending signalingincluding an identifier that identifies the first processing functionfrom a plurality of processing functions.

In Example 474, the subject matter of any one of Examples 466 to 473 canoptionally include wherein sending the signaling to the traffic filterthat specifies the first template includes sending signaling includingone or more parameters of the filter template to the traffic filter.

In Example 475, the subject matter of any one of Examples 466 to 473 canoptionally include wherein sending the signaling to the traffic filterthat specifies the first template includes sending signaling includingan identifier that identifies the filter template from a plurality offilter templates.

In Example 476, the subject matter of any one of Examples 466 to 475 canoptionally include wherein the first filter template defines one or moreparameters of target data that can filter target data from other data.

In Example 477, the subject matter of any one of Examples 466 to 476 canoptionally further include receiving processed data from the localserver that includes target data processed according to the firstprocessing function, the method further including performing cloudprocessing on the processed data to obtain output data.

In Example 478, the subject matter of Example 477 can optionally furtherinclude sending the output data to a local network that includes thelocal server.

In Example 479, the subject matter of Example 477 or 478 can optionallyfurther include receiving other data that is not target data as definedby the filter template from the traffic filter.

Example 480 is a cloud server including a controller configured toselect a first processing function for processing offload by a localserver and select a first filter template that defines target data forthe first processing function, send signaling to the local server thatspecifies the first processing function and send signaling to a trafficfilter that specifies the first filter template, select an updatedprocessing function or an updated filter template based on one or moredynamic parameters of the processing offload, and send signaling to thelocal server that specifies the updated processing function or sendsignaling to the traffic filter that specifies the updated filtertemplate.

In Example 481, the subject matter of Example 480 can optionally includewherein the controller is further configured to monitor a processingload of the local server, and configured to select the updatedprocessing function by selecting the updated processing function basedon the processing load.

In Example 482, the subject matter of Example 481 can optionally includewherein the controller is configured to select the updated processingfunction based on the processing load by determining whether theprocessing load is above a predefined threshold, and selecting theupdated processing function to have a lower processing load than thefirst processing function if the processing load is above the threshold.

In Example 483, the subject matter of Example 480 can optionally includewherein the controller is further configured to monitor a processingload of the cloud server, and is configured to select the updatedprocessing function by selecting the updated processing function basedon the processing load.

In Example 484, the subject matter of Example 483 can optionally includewherein the controller is configured to select the updated processingfunction based on the processing load by determining whether theprocessing load is above a predefined threshold, and selecting theupdated processing function to have a higher processing load than thefirst processing function if the processing load is above the threshold.

In Example 485, the subject matter of any one of Examples 480 to 484 canoptionally include wherein the controller is configured to select theupdated processing function by selecting an updated processing functionbased on a cost of transmitting data over a backhaul link, an amount ofdata being generated at a local network that includes the local server,or a power consumption of the local server.

In Example 486, the subject matter of any one of Examples 480 to 485 canoptionally include wherein the controller is configured to send thesignaling to the local server that specifies the first processingfunction by sending signaling including software for the firstprocessing function to the local server.

In Example 487, the subject matter of any one of Examples 480 to 485 canoptionally include wherein the controller is configured to send thesignaling to the local server that specifies the first processingfunction by sending signaling including an identifier that identifiesthe first processing function from a plurality of processing functions.

In Example 488, the subject matter of any one of Examples 480 to 487 canoptionally include wherein the controller is configured to send thesignaling to the traffic filter that specifies the first template bysending signaling including one or more parameters of the filtertemplate to the traffic filter.

In Example 489, the subject matter of any one of Examples 480 to 487 canoptionally include wherein the controller is configured to send thesignaling to the traffic filter that specifies the first template bysending signaling including an identifier that identifies the filtertemplate from a plurality of filter templates.

In Example 490, the subject matter of any one of Examples 480 to 489 canoptionally include wherein the first filter template defines one or moreparameters of target data that can filter target data from other data.

In Example 491, the subject matter of any one of Examples 480 to 490 canoptionally include wherein the controller is further configured toreceive processed data from the local server that includes target dataprocessed according to the first processing function, the cloud serverfurther including a processing platform including one or more processorsand configured to perform cloud processing on the processed data toobtain output data.

In Example 492, the subject matter of Example 491 can optionally includewherein the controller is further configured to send the output data toa local network that includes the local server.

In Example 493, the subject matter of Example 491 or 492 can optionallyinclude wherein the controller is further configured to receive otherdata that is not target data as defined by the filter template from thetraffic filter.

Example 494 is a method for execution at a cloud server, the methodincluding selecting a processing function for processing offload by alocal server, and selecting a filter template that defines target datafor the processing function, sending signaling to the local server thatspecifies the processing function, and sending signaling to a trafficfilter that specifies the filter template, and receiving processed datafrom a local server that is based on the filter template and theprocessing function.

Example 495 is a cloud server including a controller configured toselect a processing function for processing offload by a local server,and select a filter template that defines target data for the processingfunction, send signaling to the local server that specifies theprocessing function, and send signaling to a traffic filter thatspecifies the filter template, and receive processed data from a localserver that is based on the filter template and the processing function.

Example 496 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 397 to418, 456 to 479, or 494.

Example 497 is a device including one or more processors, and a memorystoring instructions that when executed by the one or more processorscause the one or more processors to perform the method of any one ofExamples 397 to 418, 456 to 479, or 494.

Example 498 is a device including means for receiving signaling from acloud server that specifies a processing function assigned forprocessing offload by the local server, means for receiving, from atraffic filter, target data that originates from a local network, meansfor applying the processing function to the target data to obtainprocessed data, and means for sending the processed data to the cloudserver for cloud processing.

Example 499 is a local server including means for selecting a processingfunction for processing offload, means for receiving, from a trafficfilter, target data that originates from a local network, means forapplying the processing function to the target data to obtain processeddata, and means for sending the processed data to the cloud server forcloud processing.

Example 500 is a local server including means for receiving signalingfrom a cloud server that specifies a processing function assigned forprocessing offload by the local server, means for receiving, from atraffic filter, target data that originates from a local network, meansfor applying the processing function to the target data to obtainprocessed data, and means for sending the processed data to the localnetwork.

Example 501 is a local server including means for selecting a processingfunction for processing offload, means for receiving, from a trafficfilter, target data that originates from a local network, means forapplying the processing function to the target data to obtain processeddata, and means for sending the processed data to the local network.

Example 502 is a communication device including means for receivingsignaling that specifies a filter template defining one or moreparameters of target data, means for applying the filter template to rawdata originating from a local network, means for identifying target datafrom the raw data based on the one or more parameters, and means forrouting the target data to a local server for processing offload.

Example 503 is a cloud server including means for selecting a firstprocessing function for processing offload by a local server, and meansfor selecting a first filter template that defines target data for thefirst processing function, means for sending signaling to the localserver that specifies the first processing function, and means forsending signaling to a traffic filter that specifies the first filtertemplate, means for selecting an updated processing function or anupdated filter template based on one or more dynamic parameters of theprocessing offload, and means for sending signaling to the local serverthat specifies the updated processing function or sending signaling tothe traffic filter that specifies the updated filter template.

Example 504 is a cloud server including means for selecting a processingfunction for processing offload by a local server, and selecting afilter template that defines target data for the processing function,means for sending signaling to the local server that specifies theprocessing function, and sending signaling to a traffic filter thatspecifies the filter template, and means for receiving processed datafrom a local server that is based on the filter template and theprocessing function.

Example 505 is a communication device including a biased received powerdeterminer configured to determine biased received powers for aplurality of network access nodes based on respective bias values forthe plurality of network access nodes, a comparator configured toidentify a maximum biased received power from the biased receivedpowers, and to identify a corresponding network access node of theplurality of network access nodes having the maximum biased receivedpower, and a selection controller configured to select the networkaccess node as a target network access node for the terminal device toassociate with.

In Example 506, the subject matter of Example 505 can optionally includewherein the respective bias values are based on a capability of theplurality of network access nodes to support a terminal deviceapplication of the terminal device.

In Example 507, the subject matter of Example 505 can optionally furtherinclude a distance determiner configured to determine a distance betweenthe terminal device and each of the plurality of network access nodes.

In Example 508, the subject matter of Example 507 can optionally includewherein the biased received power determiner is configured to determinethe biased received power for a first network access node of theplurality of network access nodes based on the distance between theterminal device and the first network access node.

In Example 509, the subject matter of Example 505 can optionally furtherinclude a distance determiner configured to determine a distance betweenthe terminal device and each of a plurality of candidate network accessnodes, wherein the plurality of candidate network access nodes includecandidate network access nodes of a first tier and candidate networkaccess nodes of a second tier, identify a benchmark network access nodefrom the plurality of candidate network access nodes for each of themultiple tiers having a minimum distance to the terminal device, andprovide the benchmark network access nodes to the biased received powerdeterminer as the plurality of network access nodes.

In Example 510, the subject matter of Example 509 can optionally includewherein each of the multiple tiers is assigned a respective one of thebias values.

In Example 511, the subject matter of any one of Examples 505 to 508 canoptionally include wherein the biased received power determiner isconfigured to determine the biased received power for a first networkaccess node of the plurality of network access nodes based on a distancebetween the first network access node and the terminal device, and therespective bias value for the first network access node.

In Example 512, the subject matter of Example 511 can optionally includewherein the biased received power determiner is configured to determinethe biased received power for the first network access node byestimating a received power based on the distance, and biasing thereceived power with the respective bias value for the first networkaccess node.

In Example 513, the subject matter of any one of Examples 505 to 512 canoptionally include wherein the comparator is configured to identify themaximum biased received power by comparing the biased received powers toidentify a biased received power with a highest value.

In Example 514, the subject matter of any one of Examples 505 to 513 canoptionally include wherein the target network access node is a downlinknetwork access node for the terminal device to associate with, andwherein the biased received power determiner is further configured todetermine uplink biased received powers for the plurality of networkaccess nodes based on respective uplink bias values for the plurality ofnetwork access nodes, wherein the comparator is configured to identify amaximum biased uplink received power from the biased receive powers andidentify a second target network access node from the plurality ofnetwork access nodes having the maximum biased uplink received power,and wherein the selection controller is configured to select the secondtarget network access node as an uplink network access node to for theterminal device to associate with.

In Example 515, the subject matter of any one of Examples 505 to 513 canoptionally include wherein the target network access node is an uplinknetwork access node for the terminal device to associate with, andwherein the biased received power determiner is further configured todetermine downlink biased received powers for the plurality of networkaccess nodes based on respective downlink bias values for the pluralityof network access nodes, the comparator is configured to identify amaximum biased downlink received power from the biased receive powersand identify a second target network access node from the plurality ofnetwork access nodes having the maximum biased downlink received power,and the selection controller is configured to select the second targetnetwork access node as a downlink network access node for the terminaldevice to associate with.

In Example 516, the subject matter of any one of Examples 505 to 515 canoptionally include wherein the respective bias value for a first networkaccess node of the plurality of network access nodes is based on datarate and computational capacity capabilities of the first network accessnode.

In Example 517, the subject matter of any one of Examples 505 to 515 canoptionally include wherein the respective bias value for a first networkaccess node of the plurality of network access nodes is based on datarate and computational capacity capabilities of the first network accessnode in comparison to data rate and latency demands of the terminaldevice application.

In Example 518, the subject matter of any one of Examples 505 to 515 canoptionally include wherein the respective bias value for a first networkaccess node of the plurality of network access nodes is based on acomputational capacity of an edge computing server co-located with thefirst network access node.

In Example 519, the subject matter of any one of Examples 505 to 518 canoptionally include wherein the selection controller is furtherconfigured to transmit control signaling to the terminal device or thetarget network access node to instruct the terminal device to associatewith the target network access node.

Example 520 is a communication device including a biased received powerdeterminer configured to determine biased uplink received powers for aplurality of network access nodes based on respective uplink bias valuesfor the plurality of network access nodes, and to determine biaseddownlink received powers for the plurality of network access nodes basedon respective downlink bias values for the plurality of network accessnodes, a comparator configured to evaluate the biased uplink receivedpowers and the biased downlink received powers to identify a maximumbiased uplink received power and a maximum biased downlink receivedpower, and a selection controller configured to select an uplink networkaccess node and a downlink network access node for the terminal deviceto associate with based on the maximum biased uplink received power andthe maximum biased downlink received power.

In Example 521, the subject matter of Example 520 can optionally includewherein the respective uplink bias values are based on a capability ofthe plurality of network access nodes to support the terminal device inan uplink direction and wherein the respective downlink bias values arebased on a capability of the plurality of network access nodes tosupport the terminal device application in a downlink direction.

In Example 522, the subject matter of Example 520 can optionally includewherein the comparator is configured to evaluate the biased uplinkreceived powers and the biased downlink received powers by comparing thebiased uplink received powers to identify the maximum biased uplinkreceived power, and comparing the biased downlink received powers toidentify the maximum biased downlink received power.

In Example 523, the subject matter of Example 522 can optionally includewherein the selection controller configured to select the uplink networkaccess node and the downlink network access node for the terminal deviceto associate with by selecting the network access node from theplurality of network access nodes having the maximum biased uplinkreceived power as the uplink network access node, and selecting thenetwork access node from the plurality of network access nodes havingthe maximum biased downlink received power as the downlink networkaccess node.

In Example 524, the subject matter of any one of Examples 520 to 523 canoptionally further include a distance determiner configured to determinea distance between the terminal device and the plurality of networkaccess nodes, wherein the biased received power determiner is configuredto determine the biased uplink received powers and the biased downlinkreceived powers based on the distances.

In Example 525, the subject matter of any one of Examples 520 to 523 canoptionally further include a distance determiner configured to determinea distance between the terminal device and each of a plurality ofcandidate network access nodes, wherein the plurality of candidatenetwork access nodes include candidate network access nodes of a firsttier and candidate network access nodes of a second tier, identify abenchmark network access node from the plurality of candidate networkaccess nodes for each of the multiple tiers having a minimum distance tothe terminal device, and provide the benchmark network access nodes tothe biased received power determiner as the plurality of network accessnodes.

In Example 526, the subject matter of any one of Examples 520 to 525 canoptionally include wherein the respective uplink and downlink biasvalues for a first network access node of the plurality of networkaccess nodes are based on data rate and computational capacitycapabilities of the first network access node.

In Example 527, the subject matter of any one of Examples 520 to 525 canoptionally include wherein the respective uplink and downlink biasvalues for a first network access node of the plurality of networkaccess nodes are based on data rate and computational capacitycapabilities of the first network access node in comparison to data rateand latency demands of the terminal device application.

In Example 528, the subject matter of any one of Examples 520 to 525 canoptionally include wherein the respective uplink and downlink biasvalues for a first network access node of the plurality of networkaccess nodes are based on a computational capacity of an edge computingserver co-located with the first network access node.

In Example 529, the subject matter of any one of Examples 520 to 528 canoptionally include wherein the selection controller is furtherconfigured to transmit control signaling to the terminal device toinstruct the terminal device to associate with the uplink network accessnode and the downlink network access node.

In Example 530, the subject matter of any one of Examples 520 to 529 canoptionally include wherein the uplink network access node is co-locatedwith first edge computing server and the downlink network access node isco-located with a second edge computing sever, and wherein the selectioncontroller is configured to select, based on a downlink-to-uplinktraffic ratio of the terminal device application, the first edgecomputing server or the second edge computing server for hosting a peerapplication to the terminal device application.

Example 531 is a terminal device including the communication device ofany one of Examples 505 to 530.

Example 532 is a network access node including the communication deviceof any one of Examples 505 to 530.

Example 533 is a core network server including the communication deviceof any one of Examples 505 to 530.

Example 534 is a server device including an input data memory configuredto obtain first parameters related to data rate and latency demands of aterminal device application and to obtain second parameters related todata rate and computational capacity capabilities of a plurality ofnetwork access nodes, and a bias processor configured to determine biasvalues for the plurality of network access nodes based on an evaluationof the first parameters and the second parameters, wherein the biasvalues are based on a capability of the plurality of network accessnodes to support the terminal device application.

In Example 535, the subject matter of Example 531 can optionally includewherein the bias processor is configured to determine the bias valuesfor the plurality of network access nodes using stochastic geometry.

In Example 536, the subject matter of Example 531 or 532 can optionallyinclude wherein the first parameters include information about Qualityof Service (QoS) requirements of the terminal device application.

In Example 537, the subject matter of Example 531 or 532 can optionallyinclude wherein the second parameters include information aboutdeployment densities of the plurality of network access nodes or aboutthe computational capacity of edge computing servers co-located with theplurality of network access nodes.

In Example 538, the subject matter of any one of Examples 531 to 534 canoptionally include wherein the plurality of candidate network accessnodes include network access nodes of a first tier and network accessnodes of a second tier, and wherein the bias processor is configured todetermine same bias values for the network access nodes of the firsttier and same bias values for the network access nodes of the secondtier.

In Example 539, the subject matter of any one of Examples 531 to 534 canoptionally include wherein the bias processor is configured to determinea bias value for a first network access node of the plurality of networkaccess nodes based on the data rate and computational capacitycapabilities of the first network access node.

Example 540 is a method of controlling cell association, the methodincluding determining biased received powers for a plurality of networkaccess nodes based on respective bias values for the plurality ofnetwork access nodes, identifying a maximum biased received power fromthe biased received powers and identifying a corresponding networkaccess node of the plurality of network access nodes having the maximumbiased received power, and selecting the network access node as a targetnetwork access node for the terminal device to associate with.

In Example 541, the subject matter of Example 540 can optionally includewherein the respective bias values are based on a capability of theplurality of network access nodes to support a terminal deviceapplication of a terminal device.

In Example 542, the subject matter of Example 540 can optionally furtherinclude determining a distance between the terminal device and each ofthe plurality of network access nodes.

In Example 543, the subject matter of Example 542 can optionally includewherein determining the biased received powers includes determining abiased received power for a first network access node of the pluralityof network access nodes based on the distance between the terminaldevice and the first network access node.

In Example 544, the subject matter of Example 540 can optionally furtherinclude determining a distance between the terminal device and each of aplurality of candidate network access nodes, wherein the plurality ofcandidate network access nodes include candidate network access nodes ofa first tier and candidate network access nodes of a second tier,identifying a benchmark network access node from the plurality ofcandidate network access nodes for each of the multiple tiers having aminimum distance to the terminal device, and providing the benchmarknetwork access nodes to the biased received power determiner as theplurality of network access nodes.

In Example 545, the subject matter of Example 544 can optionally includewherein each of the multiple tiers is assigned a respective one of thebias values.

In Example 546, the subject matter of any one of Examples 540 to 543 canoptionally include wherein determining the biased received powersincludes determining a biased received power for a first network accessnode of the plurality of network access nodes based on a distancebetween the first network access node and the terminal device, and therespective bias value for the first network access node.

In Example 547, the subject matter of Example 546 can optionally includewherein determining the biased received power for the first networkaccess node includes estimating a received power based on the distanceand biasing the received power with the respective bias value for thefirst network access node.

In Example 548, the subject matter of any one of Examples 540 to 547 canoptionally include wherein identifying the maximum biased received powerincludes comparing the biased received powers to identify a biasedreceived power with a highest value.

In Example 549, the subject matter of any one of Examples 540 to 548 canoptionally include wherein the target network access node is a downlinknetwork access node for the terminal device to associate with, themethod further including determining uplink biased received powers forthe plurality of network access nodes based on respective uplink biasvalues for the plurality of network access nodes, identifying a maximumbiased uplink received power from the biased receive powers andidentifying a second target network access node from the plurality ofnetwork access nodes having the maximum biased uplink received power,and selecting the second target network access node as an uplink networkaccess node for the terminal device to associate with.

In Example 550, the subject matter of any one of Examples 540 to 548 canoptionally include wherein the target network access node is an uplinknetwork access node for the terminal device to associate with, themethod further including determining downlink biased received powers forthe plurality of network access nodes based on respective downlink biasvalues for the plurality of network access nodes, identifying a maximumbiased downlink received power from the biased receive powers andidentifying a second target network access node from the plurality ofnetwork access nodes having the maximum biased downlink received power,and selecting the second target network access node as a downlinknetwork access node for the terminal device to associate with.

In Example 551, the subject matter of any one of Examples 540 to 550 canoptionally include wherein the respective bias value for a first networkaccess node of the plurality of network access nodes is based on datarate and computational capacity capabilities of the first network accessnode.

In Example 552, the subject matter of any one of Examples 540 to 550 canoptionally include wherein the respective bias value for a first networkaccess node of the plurality of network access nodes is based on datarate and computational capacity capabilities of the first network accessnode in comparison to data rate and latency demands of the terminaldevice application.

In Example 553, the subject matter of any one of Examples 540 to 550 canoptionally include wherein the respective bias value for a first networkaccess node of the plurality of network access nodes is based on acomputational capacity of an edge computing server co-located with thefirst network access node.

In Example 554, the subject matter of any one of Examples 540 to 550 canoptionally further include transmitting control signaling to theterminal device or the target network access node to instruct theterminal device to associate with the target network access node.

Example 555 is a method of controlling cell association, the methodincluding determining biased uplink received powers for a plurality ofnetwork access nodes based on respective uplink bias values for theplurality of network access nodes, determining biased downlink receivedpowers for the plurality of network access nodes based on respectivedownlink bias values for the plurality of network access nodes,evaluating the biased uplink received powers and the biased downlinkreceived powers to identify a maximum biased uplink received power and amaximum biased downlink received power, and selecting an uplink networkaccess node and a downlink network access node for the terminal deviceto associate with based on the maximum biased uplink received power andthe maximum biased downlink received power.

In Example 556, the subject matter of Example 555 can optionally includewherein the respective uplink bias values are based on a capability ofthe plurality of network access nodes to support the terminal device inan uplink direction and wherein the respective downlink bias values arebased on a capability of the plurality of network access nodes tosupport the terminal device application in a downlink direction.

In Example 557, the subject matter of Example 555 can optionally includewherein evaluating the biased uplink received powers and the biaseddownlink received powers includes comparing the biased uplink receivedpowers to identify the maximum biased uplink received power, andcomparing the biased downlink received powers to identify the maximumbiased downlink received power.

In Example 558, the subject matter of Example 557 can optionally includewherein selecting the uplink network access node and the downlinknetwork access node for the terminal device to associate with includesselecting the network access node from the plurality of network accessnodes having the maximum biased uplink received power as the uplinknetwork access node, and selecting the network access node from theplurality of network access nodes that corresponds to the maximum biaseddownlink received power as the downlink network access node.

In Example 559, the subject matter of any one of Examples 555 to 558 canoptionally further include determining a distance between the terminaldevice and the plurality of network access nodes, wherein thedetermining the biased uplink received powers and the biased downlinkreceived powers includes determining the biased uplink received powersand the biased downlink received powers based on the distances.

In Example 560, the subject matter of any one of Examples 555 to 558 canoptionally further include determining a distance between the terminaldevice and each of a plurality of candidate network access nodes,wherein the plurality of candidate network access nodes includecandidate network access nodes of a first tier and candidate networkaccess nodes of a second tier, identifying a benchmark network accessnode from the plurality of candidate network access nodes for each ofthe multiple tiers having a minimum distance to the terminal device, andproviding the benchmark network access nodes to the biased receivedpower determiner as the plurality of network access nodes.

In Example 561, the subject matter of any one of Examples 555 to 560 canoptionally include wherein the respective uplink and downlink biasvalues for a first network access node of the plurality of networkaccess nodes are based on data rate and computational capacitycapabilities of the first network access node.

In Example 562, the subject matter of any one of Examples 555 to 560 canoptionally include wherein the respective uplink and downlink biasvalues for a first network access node of the plurality of networkaccess nodes are based on data rate and computational capacitycapabilities of the first network access node in comparison to data rateand latency demands of the terminal device application.

In Example 563, the subject matter of any one of Examples 555 to 560 canoptionally include wherein the respective uplink and downlink biasvalues for a first network access node of the plurality of networkaccess nodes are based on a computational capacity of an edge computingserver co-located with the first network access node.

In Example 564, the subject matter of any one of Examples 555 to 563 canoptionally further include transmitting control signaling to theterminal device to instruct the terminal device to associate with theuplink network access node and the downlink network access node.

In Example 565, the subject matter of any one of Examples 520 to 529 canoptionally include wherein the uplink network access node is co-locatedwith first edge computing server and the downlink network access node isco-located with a second edge computing sever, the method furtherincluding selecting, based on a downlink-to-uplink traffic ratio of theterminal device application, the first edge computing server or thesecond edge computing server for hosting a peer application to theterminal device application.

Example 566 is a method of determining bias values, the method includingobtaining first parameters related to data rate and latency demands of aterminal device application and obtaining second parameters related todata rate and computational capacity capabilities of a plurality ofnetwork access nodes, and determining bias values for the plurality ofnetwork access nodes based on an evaluation of the first parameters andthe second parameters, wherein the bias values are based on a capabilityof the plurality of network access nodes to support the terminal deviceapplication.

In Example 567, the subject matter of Example 566 can optionally includewherein determining the bias values for the plurality of network accessnodes includes using stochastic geometry to determine the bias values.

In Example 568, the subject matter of Example 566 or 567 can optionallyinclude wherein the first parameters include information about Qualityof Service (QoS) requirements of the terminal device application.

In Example 569, the subject matter of Example 566 or 567 can optionallyinclude wherein the second parameters include information aboutdeployment densities of the plurality of network access nodes or aboutthe computational capacity of edge computing servers co-located with theplurality of network access nodes.

In Example 570, the subject matter of any one of Examples 566 to 569 canoptionally include wherein the plurality of candidate network accessnodes include network access nodes of a first tier and network accessnodes of a second tier, and wherein determining the bias values includesdetermining same bias values for the network access nodes of the firsttier and same bias values for the network access nodes of the secondtier.

In Example 571, the subject matter of any one of Examples 566 to 569 canoptionally include wherein determining the bias values includesdetermining a bias value for a first network access node of theplurality of network access nodes based on the data rate andcomputational capacity capabilities of the first network access node.

Example 572 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 540 to571.

Example 573 is a device including one or more processors, and a memorystoring instructions that when executed by the one or more processorscause the one or more processors to perform the method of any one ofExamples 540 to 571.

Example 574 is a communication device including determining meansconfigured to determine biased received powers for a plurality ofnetwork access nodes based on respective bias values for the pluralityof network access nodes, comparing means configured to identify amaximum biased received power from the biased received powers, and toidentify a corresponding network access node of the plurality of networkaccess nodes having the maximum biased received power, and selectingmeans configured to select the network access node as a target networkaccess node for the terminal device to associate with.

Example 575 is a communication device including determining meansconfigured to determine biased uplink received powers for a plurality ofnetwork access nodes based on respective uplink bias values for theplurality of network access nodes, and to determine biased downlinkreceived powers for the plurality of network access nodes based onrespective downlink bias values for the plurality of network accessnodes, comparing means configured to evaluate the biased uplink receivedpowers and the biased downlink received powers to identify a maximumbiased uplink received power and a maximum biased downlink receivedpower, and selecting means configured to select an uplink network accessnode and a downlink network access node for the terminal device toassociate with based on the maximum biased uplink received power and themaximum biased downlink received power.

Example 576 is a server device including collecting means configured toobtain first parameters related to data rate and latency demands of aterminal device application and to obtain second parameters related todata rate and computational capacity capabilities of a plurality ofnetwork access nodes, and processing means configured to determine biasvalues for the plurality of network access nodes based on an evaluationof the first parameters and the second parameters, wherein the biasvalues are based on a capability of the plurality of network accessnodes to support the terminal device application.

The subject matter of Example 577 is a communication device including afirst receiver configured to receive a scheduling message for at leastone further communication device, a processor configured to generate ascheduling message and process the generated scheduling message and thereceived scheduling message to determine at least one schedulingparameter for transmit data, and a transmitter configured to transmitthe data based on the at least one scheduling parameter.

In Example 578, the subject matter of Example 577 can optionally includewherein each scheduling message includes first priority information, andthe processor is configured to determine the scheduling parameter basedon a comparison of first priority information of the generatedscheduling message with first priority information of the receivedscheduling message.

In Example 579, the subject matter of any one of Examples 577 to 578 canoptionally include wherein the transmitter is configured to transmit thegenerated scheduling message to the at least one further communicationdevice within a scheduling time interval during which the first receiveris configured to receive the scheduling message.

In Example 580, the subject matter of Example 579 can optionally includewherein a transmission time during which the transmitter is configuredto transmit the generated scheduling message at least partially or fullyoverlaps with a reception time during which the first receiver isconfigured to receive the scheduling message.

In Example 581, the subject matter of any one of Examples 579 to 580 canoptionally further include a second receiver configured to receive aclock signal defining the scheduling time interval.

In Example 582, the subject matter of Example 581 can optionally includewherein the second receiver is configured to receive the clock signalfrom at least one of a group consisting of a satellite, a base stationof a communication network, and at least one further communicationdevice.

In Example 583, the subject matter of any one of Examples 577 to 582 canoptionally include wherein the transmitter is configured to transmit thegenerated scheduling message to the at least one further communicationdevice using at least one communication frequency and wherein the firstreceiver is configured to receive the scheduling message using the sameat least one communication frequency.

In Example 584, the subject matter of any one of Examples 579 to 583 canoptionally include the communication device being configured to operatein a full duplex operation mode at least during the scheduling timeinterval.

In Example 585, the subject matter of any one of Examples 577 to 584 canoptionally include wherein a transmission format of each schedulingmessage is predefined, and wherein upon processing the generatedscheduling message and the received scheduling message, the processor isconfigured to reconstruct the received scheduling message from a signalreceived by the first receiver based on a respective predefined formatof the received scheduling message.

In Example 586, the subject matter of Example 585 can optionally includewherein the processor is configured to perform interference cancellationprocessing to reconstruct the received scheduling message from thesignal received by the first receiver.

In Example 587, the subject matter of any one of Examples 578 to 586 canoptionally include wherein each scheduling message further includessecond priority information, and the processor is configured todetermine the scheduling parameter based on a comparison of secondpriority information of the generated scheduling message with secondpriority information of the received scheduling message when the firstpriority information of the generated scheduling message matches thefirst priority information of the received scheduling message.

In Example 588, the subject matter of any one of Examples 578 to 587 canoptionally include wherein the first priority information is determinedby the communication device for a type of data to be transmitted or ispredefined for a type of data to be transmitted.

In Example 589, the subject matter of any one of Examples 587 to 588 canoptionally include wherein the second priority information is an offsetvalue determined for each scheduling message.

In Example 590, the subject matter of any one of Examples 587 to 589 canoptionally include wherein the processor is configured to generate thesecond priority information for the generated scheduling message.

In Example 591, the subject matter of any one of Examples 577 to 590 canoptionally include wherein the at least one scheduling parameter definesa transmission time interval and the transmitter is configured totransmit the data during the transmission time interval.

In Example 592, the subject matter of any one of Examples 577 to 591 canoptionally include wherein the at least one scheduling parameter definesa frequency resource and the transmitter is configured to transmit thedata using the frequency resource.

In Example 593, the subject matter of any one of Examples 577 to 592 canoptionally include wherein the generated scheduling message includesinformation on a transmission power for transmit data from thecommunication device and the received scheduling message includesinformation on a transmission power for transmit data from the at leastone further communication device, and the processor is configured todetermine the scheduling parameter based on a comparison of theinformation on the transmission power of the generated schedulingmessage with the information on the transmission power of the receivedscheduling message.

In Example 594, the subject matter of any one of Examples 577 to 593 canoptionally include wherein the generated scheduling message includesinformation on a modulation scheme for transmit data from thecommunication device and the received scheduling message includesinformation on a modulation scheme for transmit data from the at leastone further communication device, and the processor is configured todetermine the scheduling parameter based on a comparison of theinformation on the modulation scheme of the generated scheduling messagewith the information on the modulation scheme of the received schedulingmessage.

In Example 595, the subject matter of any one of Examples 577 to 594 canoptionally include wherein the generated scheduling message includesinformation on a coding rate for transmit data from the communicationdevice and the received scheduling message includes information on acoding rate for transmit data from the at least one furthercommunication device, and the processor is configured to determine thescheduling parameter based on a comparison of the information on thecoding rate of the generated scheduling message with the information onthe coding rate of the received scheduling message.

The subject matter of Example 596 is a communication method for acommunication device, the method including generating a schedulingmessage, receiving a scheduling message for at least one furthercommunication device, processing the generated scheduling message andthe received scheduling message to determine at least one schedulingparameter for transmit data, and transmitting the data based on the atleast one scheduling parameter.

In Example 597, the subject matter of Example 596 can optionally includewherein each scheduling message includes first priority information, andthe processing includes determining the scheduling parameter based on acomparison of first priority information of the generated schedulingmessage with first priority information of the received schedulingmessage.

In Example 598, the subject matter of any one of Examples 596 to 597 canoptionally further include transmitting the generated scheduling messageto the at least one further communication device within a schedulingtime interval during which the scheduling message for the at least onefurther communication device is received.

In Example 599, the subject matter of Example 598 can optionally includewherein transmitting the generated scheduling message is performedduring a transmission time and receiving the scheduling message isperformed during a reception time, the transmission time and thereception time at least partially or fully overlapping.

In Example 600, the subject matter of any one of Examples 598 to 599 canoptionally further include receiving a clock signal defining thescheduling time interval.

In Example 601, the subject matter of Example 600 can optionally furtherinclude receiving the clock signal from at least one of a groupconsisting of a satellite, a base station of a communication network,and at least one further communication device.

In Example 602, the subject matter of any one of Examples 596 to 601 canoptionally include wherein transmitting the generated scheduling messageto the at least one further communication device is performed using atleast one communication frequency and wherein receiving the schedulingmessage is performed using the same at least one communicationfrequency.

In Example 603, the subject matter of any one of Examples 598 to 602 canoptionally further include operating the communication device in a fullduplex operation mode at least during the scheduling time interval.

In Example 604, the subject matter of any one of Examples 596 to 603 canoptionally include wherein a transmission format of each schedulingmessage is predefined, and wherein processing the generated schedulingmessage includes reconstructing the received scheduling message from areceived signal based on a respective predefined format of the receivedscheduling message.

In Example 605, the subject matter of Example 604 can optionally includewherein the processing includes performing interference cancellationprocessing to reconstruct the received scheduling message from thereceived signal.

In Example 606, the subject matter of any one of Examples 597 to 605 canoptionally include wherein each scheduling message further includessecond priority information, and the processing includes determining thescheduling parameter based on a comparison of second priorityinformation of the generated scheduling message with second priorityinformation of the received scheduling message when the first priorityinformation of the generated scheduling message matches the firstpriority information of the received scheduling message.

In Example 607, the subject matter of any one of Examples 597 to 606 canoptionally further include generating the first priority information fora type of data to be transmitted or selecting a predefined firstpriority information for a type of data to be transmitted.

In Example 608, the subject matter of any one of Examples 606 to 607 canoptionally further include determining the second priority informationas an offset value for each scheduling message.

In Example 609, the subject matter of any one of Examples 606 to 608 canoptionally further include generating the second priority informationfor the generated scheduling message.

In Example 610, the subject matter of any one of Examples 596 to 609 canoptionally include wherein the at least one scheduling parameter definesa transmission time interval and transmitting the data is performedduring the transmission time interval.

In Example 611, the subject matter of any one of Examples 596 to 610 canoptionally include wherein the at least one scheduling parameter definesa frequency resource and transmitting the data is performed using thefrequency resource.

In Example 612, the subject matter of any one of Examples 596 to 611 canoptionally include wherein the generated scheduling message includesinformation on a transmission power for transmit data from thecommunication device and the received scheduling message includesinformation on a transmission power for transmit data from the at leastone further communication device, and the processing includesdetermining the scheduling parameter based on a comparison of theinformation on the transmission power of the generated schedulingmessage with the information on the transmission power of the receivedscheduling message.

In Example 613, the subject matter of any one of Examples 596 to 612 canoptionally include wherein the generated scheduling message includesinformation on a modulation scheme for transmit data from thecommunication device and the received scheduling message includesinformation on a modulation scheme for transmit data from the at leastone further communication device, and the processing includesdetermining the scheduling parameter based on a comparison of theinformation on the modulation scheme of the generated scheduling messagewith the information on the modulation scheme of the received schedulingmessage.

In Example 614, the subject matter of any one of Examples 596 to 613 canoptionally include wherein the generated scheduling message includesinformation on a coding rate for transmit data from the communicationdevice and the received scheduling message includes information on acoding rate for transmit data from the at least one furthercommunication device, and the processing includes determining thescheduling parameter based on a comparison of the information on thecoding rate of the generated scheduling message with the information onthe coding rate of the received scheduling message.

The subject matter of Example 615 is a communication device includingone or more processors configured to generate a scheduling message,receive a scheduling message for at least one further communicationdevice, process the generated scheduling message and the receivedscheduling message to determine at least one scheduling parameter fortransmit data, and transmit the data in accordance with the determinedat least one scheduling parameter.

In Example 616, the subject matter of Example 615 can optionally includewherein each scheduling message includes first priority information, andthe one or more processors are configured to determine the schedulingparameter based on a comparison of first priority information of thegenerated scheduling message with first priority information of thereceived scheduling message.

In Example 617, the subject matter of any one of Examples 615 to 616 canoptionally include wherein the one or more processors are configured totransmit the generated scheduling message to the at least one furthercommunication device within a scheduling time interval during which theone or more processors are configured to receive the scheduling message.

In Example 618, the subject matter of Example 617 can optionally includewherein a transmission time during which the one or more processors areconfigured to transmit the generated scheduling message at leastpartially or fully overlaps with a reception time during which the oneor more processors are configured to receive the scheduling message.

In Example 619, the subject matter of any one of Examples 617 to 618 canoptionally include wherein the one or more processors are furtherconfigured to receive a clock signal defining the scheduling timeinterval.

In Example 620, the subject matter of Example 619 can optionally includewherein the one or more processors are configured to receive the clocksignal from at least one of a group consisting of a satellite, a basestation of a communication network, and at least one furthercommunication device.

In Example 621, the subject matter of any one of Examples 615 to 620 canoptionally include wherein the one or more processors are configured totransmit the generated scheduling message to the at least one furthercommunication device using at least one communication frequency andwherein the one or more processors are configured to receive thescheduling message using the same at least one communication frequency.

In Example 622, the subject matter of any one of Examples 617 to 621 canoptionally include wherein the one or more processors are configured tocause the communication device to operate in a full duplex operationmode at least during the scheduling time interval.

In Example 623, the subject matter of any one of Examples 615 to 622 canoptionally include wherein a transmission format of each schedulingmessage is predefined, and wherein upon processing the generatedscheduling message and the received scheduling message, the one or moreprocessors are configured to reconstruct the received scheduling messagefrom a signal received by the first receiver based on a respectivepredefined format of the received scheduling message.

In Example 624, the subject matter of Example 623 can optionally includewherein the one or more processors are configured to performinterference cancellation processing to reconstruct the receivedscheduling message from the signal received by the one or moreprocessors.

In Example 625, the subject matter of any one of Examples 616 to 624 canoptionally include wherein each scheduling message further includessecond priority information, and the one or more processors areconfigured to determine the scheduling parameter based on a comparisonof second priority information of the generated scheduling message withsecond priority information of the received scheduling message when thefirst priority information of the generated scheduling message matchesthe first priority information of the received scheduling message.

In Example 626, the subject matter of any one of Examples 616 to 625 canoptionally include wherein the first priority information is determinedby the communication device for a type of data to be transmitted or ispredefined for a type of data to be transmitted.

In Example 627, the subject matter of any one of Examples 616 to 626 canoptionally include wherein the second priority information is an offsetvalue determined for each scheduling message.

In Example 628, the subject matter of any one of Examples 625 to 627 canoptionally include wherein the one or more processors are configured togenerate the second priority information for the generated schedulingmessage.

In Example 629, the subject matter of any one of Examples 615 to 628 canoptionally include wherein the at least one scheduling parameter definesa transmission time interval and the one or more processors areconfigured to transmit the data during the transmission time interval.

In Example 630, the subject matter of any one of Examples 615 to 629 canoptionally include wherein the at least one scheduling parameter definesa frequency resource and the one or more processors are configured totransmit the data using the frequency resource.

In Example 631, the subject matter of any one of Examples 615 to 630 canoptionally include wherein the generated scheduling message includesinformation on a transmission power for transmit data from thecommunication device and the received scheduling message includesinformation on a transmission power for transmit data from the at leastone further communication device, and the one or more processors areconfigured to determine the scheduling parameter based on a comparisonof the information on the transmission power of the generated schedulingmessage with the information on the transmission power of the receivedscheduling message.

In Example 632, the subject matter of any one of Examples 615 to 631 canoptionally include wherein the generated scheduling message includesinformation on a modulation scheme for transmit data from thecommunication device and the received scheduling message includesinformation on a modulation scheme for transmit data from the at leastone further communication device, and the one or more processors areconfigured to determine the scheduling parameter based on a comparisonof the information on the modulation scheme of the generated schedulingmessage with the information on the modulation scheme of the receivedscheduling message.

In Example 633, the subject matter of any one of Examples 615 to 632 canoptionally include wherein the generated scheduling message includesinformation on a coding rate for transmit data from the communicationdevice and the received scheduling message includes information on acoding rate for transmit data from the at least one furthercommunication device, and the one or more processors are configured todetermine the scheduling parameter based on a comparison of theinformation on the coding rate of the generated scheduling message withthe information on the coding rate of the received scheduling message.

Example 634 is a network access node including a scheduler configured toobtain a battery power status for a terminal device with a firstmodulation scheme and to select a second modulation scheme for theterminal device if the battery power status satisfies a predefinedcondition, and a transmitter configured to send a modulation schemeassignment message to the terminal device that identifies the secondmodulation scheme.

In Example 635, the subject matter of Example 634 can optionally includewherein the battery power status is a remaining battery power level forthe terminal device.

In Example 636, the subject matter of Example 635 can optionally includewherein the scheduler is configured to select the second modulationscheme for the terminal device by determining if the remaining batterypower level is less than a threshold, and selecting a modulation schemehaving a lower modulation order than the first modulation scheme as thesecond modulation scheme.

In Example 637, the subject matter of Example 634 can optionally includewherein the battery power status is a power-saving mode indicator thatindicates whether a power-saving mode of the terminal device is enabled.

In Example 638, the subject matter of Example 637 can optionally includewherein the scheduler is configured to select the second modulationscheme for the terminal device by determining whether the power-savingmode indicator indicates that the power-saving mode is enabled, andselecting a modulation scheme having a lower modulation order than thefirst modulation scheme as the second modulation scheme in response todetermining that the power-saving mode indicator indicates that thepower-saving mode is enabled.

In Example 639, the subject matter of Example 634 can optionally includewherein the scheduler is configured to select the second modulationscheme for the terminal device if a control variable satisfies apredefined condition.

In Example 640, the subject matter of Example 639 can optionally includewherein the additional control variable is a distance between theterminal device and the network access node.

In Example 641, the subject matter of Example 640 can optionally includewherein the scheduler is configured to select the second modulationscheme for the terminal device by determining whether distance isgreater than a predefined threshold, and selecting a modulation schemehaving a lower modulation order than the first modulation scheme as thesecond modulation scheme in response to determining that the distance isgreater than the predefined threshold.

In Example 642, the subject matter of Example 639 can optionally includewherein the additional control variable is a temperature of the terminaldevice.

In Example 643, the subject matter of any one of Examples 634 to 641 canoptionally include wherein the first modulation scheme is a quadratureamplitude modulation scheme and the second modulation scheme is aphase-shift keying modulation scheme.

In Example 644, the subject matter of any one of Examples 634 to 643 canoptionally include wherein the second modulation scheme has a lowermodulation order than the first modulation scheme.

In Example 645, the subject matter of any one of Examples 634 to 644 canoptionally include wherein the scheduler is configured to obtain thebattery power status for the terminal device by receiving a batterypower status report from the terminal device that indicates the batterypower status.

In Example 646, the subject matter of any one of Examples 634 to 645 canoptionally include wherein the scheduler is configured to select thesecond modulation scheme for the terminal device by selecting the secondmodulation scheme based on a predefined mapping that maps differentbattery power statuses to respective modulation schemes.

In Example 647, the subject matter of Example 646 can optionally includewherein the predefined mapping maps lower remaining battery power levelsto modulation schemes with lower modulation order.

In Example 648, the subject matter of any one of Examples 634 to 645 canoptionally include wherein the battery power status is one of aplurality of control variables for a predefined mapping that mapsdifferent battery power statuses to a plurality of predefined modulationschemes, and wherein the scheduler is configured to select the secondmodulation scheme for the terminal device by selecting the secondmodulation scheme based on the predefined mapping.

In Example 649, the subject matter of Example 648 can optionally includewherein the plurality of control variables include a distance betweenthe terminal device and the network access node, a temperature of theterminal device, or a charging status of the terminal device.

In Example 650, the subject matter of any one of Examples 634 to 649 canoptionally include wherein the scheduler is configured to send aninstruction to the terminal device to use a first radio access channeland a second radio access channel to transmit a data stream to thenetwork access node with the second modulation scheme.

In Example 651, the subject matter of Example 650 can optionally includewherein the first radio access channel is on first spectrum and thesecond radio access channel is on second spectrum.

In Example 652, the subject matter of Example 650 can optionally includewherein the first radio access channel is on licensed spectrum and thesecond radio access channel is on unlicensed spectrum.

In Example 653, the subject matter of any one of Examples 634 to 652 canoptionally further include a receiver configured to receive modulateddata from the terminal device using the second modulation scheme.

Example 654 is a terminal device including a protocol controllerconfigured to determine a battery power status for the terminal devicewhile the terminal device is assigned a first modulation scheme, and toselect a second modulation scheme for the terminal device if the batterypower status satisfies a predefined condition, and a transceiverconfigured to send a modulation scheme request message to a networkaccess node that requests assignment of the second modulation scheme tothe terminal device.

In Example 655, the subject matter of Example 654 can optionally includewherein the battery power status is a remaining battery power level.

In Example 656, the subject matter of Example 655 can optionally includewherein the protocol controller is configured to select the secondmodulation scheme for the terminal device by determining whether theremaining battery power level is less than a threshold, and selecting amodulation scheme having a lower modulation order than the firstmodulation scheme as the second modulation scheme in response todetermining that the remaining battery power level is less thanthreshold.

In Example 657, the subject matter of Example 654 can optionally includewherein the battery power status is a power-saving mode indicator thatindicates whether a power-saving mode of the terminal device is enabled.

In Example 658, the subject matter of Example 657 can optionally includewherein the protocol controller is configured to select the secondmodulation scheme for the terminal device by determining whether thepower-saving mode indicator indicates that the power-saving mode isenabled, and selecting a modulation scheme having a lower modulationorder than the first modulation scheme in response to determining thatthe power-saving mode indicator indicates that the power-saving mode isenabled.

In Example 659, the subject matter of any one of Examples 654 to 658 canoptionally include wherein the protocol controller is configured toselect the second modulation scheme for the terminal device if a controlvariable satisfies a predefined condition.

In Example 660, the subject matter of Example 659 can optionally includewherein the additional control variable is a distance between theterminal device and a network access node.

In Example 661, the subject matter of Example 659 can optionally includewherein the additional control variable is a temperature of the terminaldevice.

In Example 662, the subject matter of Example 659 can optionally includewherein the additional control variable is a charging status of theterminal device.

In Example 663, the subject matter of any one of Examples 654 to 661 canoptionally include wherein the first modulation scheme is a quadratureamplitude modulation scheme and the second modulation scheme is aphase-shift keying modulation scheme.

In Example 664, the subject matter of any one of Examples 654 to 663 canoptionally include wherein the second modulation scheme has a highermodulation order than the first modulation scheme.

In Example 665, the subject matter of any one of Examples 654 to 664 canoptionally include wherein the transceiver is further configured toreceive a modulation scheme accept message from the network access nodein response to the modulation scheme request message, the terminaldevice further including a digital signal processor configured tomodulate data with the second modulation scheme and provide the data tothe transceiver for wireless transmission to the network access node.

In Example 666, the subject matter of Example 665 can optionally includethe transceiver further configured to transmit the data to the networkaccess node.

Example 667 is a network access node including a scheduler configured toobtain a plurality of control variables for a terminal device with afirst modulation scheme and to select a second modulation scheme basedon a predefined mapping that maps control variables to modulationschemes, wherein the one or more control variables include a batterypower status, and a transmitter configured to send a modulation schemeassignment message identifying the second modulation scheme to theterminal device.

In Example 668, the subject matter of Example 667 can optionally includewherein the predefined mapping maps different values of controlvariables to respective modulation schemes of a plurality of modulationschemes.

In Example 669, the subject matter of Example 667 or 668 can optionallyinclude wherein the plurality of control variables include a temperatureof the terminal device, a distance between the terminal device and thenetwork access node, or a charging status of the terminal device.

In Example 670, the subject matter of any one of Examples 667 to 669 canoptionally include wherein the battery power status is a remainingbattery power level of the terminal device or a power-saving modeindicator that indicates whether a power-saving mode of the terminaldevice is enabled.

Example 671 is a method of operating a network access node, the methodincluding obtaining a battery power status for a terminal device with afirst modulation scheme, selecting a second modulation scheme for theterminal device if the battery power status satisfies a predefinedcondition, and sending a modulation scheme assignment message to theterminal device that identifies the second modulation scheme.

In Example 672, the subject matter of Example 671 can optionally includewherein the battery power status is a remaining battery power level forthe terminal device.

In Example 673, the subject matter of Example 672 can optionally includewherein selecting the second modulation scheme for the terminal deviceincludes determining whether remaining battery power level is less thana threshold, and selecting a modulation scheme having a lower modulationorder than the first modulation scheme as the second modulation schemein response to determining that the remaining battery power level isless than threshold.

In Example 674, the subject matter of Example 671 can optionally includewherein the battery power status is a power-saving mode indicator thatindicates whether a power-saving mode of the terminal device is enabled.

In Example 675, the subject matter of Example 674 can optionally includewherein selecting the second modulation scheme for the terminal deviceincludes determining whether power-saving mode indicator indicates thatthe power-saving mode is enabled, and selecting a modulation schemehaving a lower modulation order than the first modulation scheme as thesecond modulation scheme in response to determining that thepower-saving mode indicator indicates that the power-saving mode isenabled.

In Example 676, the subject matter of Example 671 can optionally includewherein selecting the second modulation scheme for the terminal deviceincludes selecting the second modulation scheme if a control variablesatisfies a predefined condition.

In Example 677, the subject matter of Example 676 can optionally includewherein the additional control variable is a distance between theterminal device and the network access node.

In Example 678, the subject matter of Example 677 can optionally includewherein selecting the second modulation scheme for the terminal deviceincludes determining whether distance is greater than a predefinedthreshold, and selecting a modulation scheme having a lower modulationorder than the first modulation scheme as the second modulation schemein response to determining that the distance is greater than thepredefined threshold.

In Example 679, the subject matter of Example 676 can optionally includewherein the additional control variable is a temperature of the terminaldevice.

In Example 680, the subject matter of Example 676 can optionally includewherein the additional control variable is a charging status of theterminal device.

In Example 681, the subject matter of any one of Examples 671 to 680 canoptionally include wherein the first modulation scheme is a quadratureamplitude modulation scheme and the second modulation scheme is aphase-shift keying modulation scheme.

In Example 682, the subject matter of any one of Examples 671 to 681 canoptionally include wherein the second modulation scheme has a lowermodulation order than the first modulation scheme.

In Example 683, the subject matter of any one of Examples 671 to 682 canoptionally include wherein obtaining the battery power status for theterminal device includes receiving a battery power status report fromthe terminal device that indicates the battery power status.

In Example 684, the subject matter of any one of Examples 671 to 683 canoptionally include wherein selecting the second modulation scheme forthe terminal device includes selecting the second modulation schemebased on a predefined mapping that maps different battery power statusesto respective modulation schemes.

In Example 685, the subject matter of Example 684 can optionally includewherein the predefined mapping maps lower remaining battery power levelsto modulation schemes with lower modulation order.

In Example 686, the subject matter of any one of Examples 671 to 683 canoptionally include wherein the battery power status is one of aplurality of control variables for a predefined mapping that mapsdifferent battery power statuses to a plurality of predefined modulationschemes, and selecting the second modulation scheme for the terminaldevice includes selecting the second modulation scheme based on thepredefined mapping.

In Example 687, the subject matter of Example 686 can optionally includewherein the plurality of control variables include a distance betweenthe terminal device and the network access node, a temperature of theterminal device, or a charging status of the terminal device.

In Example 688, the subject matter of any one of Examples 671 to 687 canoptionally further include sending an instruction to the terminal deviceto use a first radio access channel and a second radio access channel totransmit a data stream to the network access node with the secondmodulation scheme.

In Example 689, the subject matter of Example 688 can optionally includewherein the first radio access channel is on first spectrum and thesecond radio access channel is on second spectrum.

In Example 690, the subject matter of Example 688 can optionally includewherein the first radio access channel is on licensed spectrum and thesecond radio access channel is on unlicensed spectrum.

In Example 691, the subject matter of any one of Examples 671 to 690 canoptionally further include receiving modulated data from the terminaldevice using the second modulation scheme.

Example 692 is a method of operating a terminal device, the methodincluding determining a battery power status of the terminal devicewhile the terminal device is assigned a first modulation scheme,selecting a second modulation scheme for the terminal device if thebattery power status satisfies a predefined condition, and sending amodulation scheme request message to a network access node that requestsassignment of the second modulation scheme to the terminal device.

In Example 693, the subject matter of Example 692 can optionally includewherein the battery power status is a remaining battery power level.

In Example 694, the subject matter of Example 693 can optionally includewherein selecting the second modulation scheme for the terminal deviceincludes determining whether the remaining battery power level is lessthan a threshold, and selecting a modulation scheme having a lowermodulation order than the first modulation scheme as the secondmodulation scheme in response to determining that the remaining batterypower level is less than threshold.

In Example 695, the subject matter of Example 692 can optionally includewherein the battery power status is a power-saving mode indicator thatindicates whether a power-saving mode of the terminal device is enabled.

In Example 696, the subject matter of Example 695 can optionally includewherein selecting the second modulation scheme for the terminal deviceincludes determining whether the power-saving mode indicator indicatesthat the power-saving mode is enabled, and selecting a modulation schemehaving a lower modulation order than the first modulation scheme inresponse to determining that the power-saving mode indicator indicatesthat the power-saving mode is enabled.

In Example 697, the subject matter of any one of Examples 692 to 696 canoptionally include wherein the selecting the second modulation schemefor the terminal device includes selecting the second modulation schemeif a control variable satisfies a predefined condition.

In Example 698, the subject matter of Example 697 can optionally includewherein the additional control variable is a distance between theterminal device and a network access node.

In Example 699, the subject matter of Example 697 can optionally includewherein the additional control variable is a temperature of the terminaldevice.

In Example 700, the subject matter of Example 697 can optionally includewherein the additional control variable is a charging status of theterminal device.

In Example 701, the subject matter of any one of Examples 692 to 700 canoptionally include wherein the first modulation scheme is a quadratureamplitude modulation scheme and the second modulation scheme is aphase-shift keying modulation scheme.

In Example 702, the subject matter of any one of Examples 692 to 701 canoptionally include wherein the second modulation scheme has a lowermodulation order than the first modulation scheme.

In Example 703, the subject matter of any one of Examples 692 to 702 canoptionally further include receiving a modulation scheme accept messagefrom the network access node in response to the modulation schemerequest message, and transmitting data to the network access node withthe second modulation scheme.

Example 704 is a method of operating a network access node, the methodincluding obtaining a plurality of control variables for a terminaldevice with a first modulation scheme, selecting a second modulationscheme based on a predefined mapping that maps control variables tomodulation schemes, wherein the one or more control variables include abattery power status, and sending a modulation scheme assignment messageidentifying the second modulation scheme to the terminal device.

In Example 705, the subject matter of Example 704 can optionally includewherein the predefined mapping maps different values of controlvariables to respective modulation schemes of a plurality of modulationschemes.

In Example 706, the subject matter of Example 704 or 705 can optionallyinclude wherein the plurality of control variables include a temperatureof the terminal device, a distance between the terminal device and thenetwork access node, or a charging status of the terminal device.

In Example 707, the subject matter of any one of Examples 704 to 706 canoptionally include wherein the battery power status is a remainingbattery power level of the terminal device or a power-saving modeindicator that indicates whether a power-saving mode of the terminaldevice is enabled.

Example 708 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 671 to707.

Example 709 is a device including one or more processors, and a memorystoring instructions that when executed by the one or more processorscause the device to perform the method of any one of Examples 671 to707.

Example 710 is a network access node including scheduling meansconfigured to obtain a battery power status for a terminal device with afirst modulation scheme and to select a second modulation scheme for theterminal device if that the battery power status satisfies a predefinedcondition, and transmitting means configured to send a modulation schemeassignment message to the terminal device that identifies the secondmodulation scheme.

Example 711 is a terminal device including controlling means configuredto determine a battery power status for the terminal device while theterminal device is assigned a first modulation scheme, and to select asecond modulation scheme for the terminal device if the battery powerstatus satisfies a predefined condition, and transmitting meansconfigured to send a modulation scheme request message to a networkaccess node that requests assignment of the second modulation scheme.

Example 712 is a network access node including scheduling meansconfigured to obtain a plurality of control variables for a terminaldevice with a first modulation scheme and to select a second modulationscheme based on a predefined mapping that maps control variables tomodulation schemes, wherein the one or more control variables include abattery power status, and transmitting means configured to send amodulation scheme assignment message identifying the second modulationscheme to the terminal device.

Example 713 is a communication device including a router configured totransmit or receive a data stream in a first compression format withfirst spectrum, and a controller configured to detect a triggeringcondition based on a power status of the communication device or alatency parameter of the data stream, and to select a second compressionformat and second spectrum, the router further configured to transmit orreceive the data stream in the second compression format with the firstspectrum and the second spectrum.

In Example 714, the subject matter of Example 713 can optionally includewherein the power status is a remaining battery power level of thecommunication device, and wherein the controller is configured to detectthe triggering condition by comparing the remaining battery power levelto a battery power level threshold and detecting the triggeringcondition if the remaining battery power level is less than the batterypower level threshold.

In Example 715, the subject matter of Example 713 can optionally includewherein the power status is a power-saving mode indicator that indicateswhether a power-saving mode of the communication device is enabled, andwherein the controller is configured to detect the triggering conditionif the power-saving mode indicator indicates that the power-saving modeis enabled.

In Example 716, the subject matter of Example 713 can optionally includewherein the latency parameter of the data stream is a measured latencyof the data stream, and wherein the controller is configured to detectthe triggering condition by comparing the measured latency to apredefined latency threshold and detecting the triggering condition ifthe measured latency is greater than the predefined latency threshold.

In Example 717, the subject matter of any one of Examples 713 to 716 canoptionally include wherein the router is configured to transmit orreceive the data stream in the second compression format with the firstspectrum and the second spectrum by receiving the data stream in thesecond compression format, splitting the data stream into a first partand a second part, transmitting the first part via a first transceiverthat operates on the first spectrum, and transmitting the second partvia a second transceiver that operates on the second spectrum.

In Example 718, the subject matter of any one of Examples 713 to 716 canoptionally include wherein the router is configured to transmit orreceive the data stream in the second compression format with the firstspectrum and the second spectrum by receiving a first part of the datastream in the second compression format from a first transceiver thatoperates on the first spectrum, receiving a second part of the datastream in the second compression format from a second transceiver thatoperates on the second spectrum, and recombining the first part and thesecond part to obtain the data stream in the second compression format.

In Example 719, the subject matter of Example 717 or 718 can optionallyfurther include the first transceiver and the second transceiver.

In Example 720, the subject matter of Example 719 can optionally furtherinclude a first antenna and a second antenna, wherein the firsttransceiver is configured to wirelessly transmit and receive with thefirst antenna on the first spectrum and the second transceiver isconfigured to wirelessly transmit and receive with the second antenna onthe second spectrum.

In Example 721, the subject matter of any one of Examples 713 to 720 canoptionally further include a digital compression processor configured toreceive the data stream from a stream application before the routertransmits or receives the data stream in the second compression format,apply the second compression format to the data stream, and provide thedata stream in the second compression format to the router.

In Example 722, the subject matter of Example 721 can optionally includewherein the second compression format is an uncompressed compressionformat, and wherein the digital compression processor is configured toapply the second compression format to the data stream by allowing thedata stream to pass through without compression processing.

In Example 723, the subject matter of Example 721 or 722 can optionallyfurther include the stream application, wherein the stream applicationis configured to generate the data stream in its initial format.

In Example 724, the subject matter of any one of Examples 713 to 720 canoptionally further include a digital compression processor configured toreceive the data stream from the router in the second compression formatafter the router receives the data stream in the second compressionformat, and to revert the second compression format.

In Example 725, the subject matter of Example 724 can optionally includewherein the second compression format is an uncompressed compressionformat, and wherein the digital compression processor is configured torevert the second compression format by allowing the data stream to passthrough without decompression processing.

In Example 726, the subject matter of Example 724 or 725 can optionallyfurther include a stream application, wherein the digital compressionprocessor is configured to provide the data stream to the streamapplication after reverting the second compression format.

In Example 727, the subject matter of any one of Examples 713 to 726 canoptionally include wherein transfer of the data stream in the secondcompression format has a higher data rate demand than transfer of thedata stream in the first compression format, and wherein the controlleris configured to identify the second spectrum based on the higher datarate demand.

In Example 728, the subject matter of any one of Examples 713 to 727 canoptionally include wherein the second compression format is anuncompressed compression format.

In Example 729, the subject matter of any one of Examples 713 to 727 canoptionally include wherein the second compression format is a compressedcompression format.

In Example 730, the subject matter of any one of Examples 713 to 729 canoptionally include wherein the second compression format is more powerefficient than the first compression format.

In Example 731, the subject matter of any one of Examples 713 to 730 canoptionally include wherein the second compression format has lowerlatency than the first compression format.

In Example 732, the subject matter of any one of Examples 713 to 731 canoptionally include wherein the second compression format has lowercompression efficiency than the first compression format.

Example 733 is a communication device including a router configured totransmit or receive a data stream in a first compression format withfirst spectrum, and a controller configured to detect a triggeringcondition based on a power status of the communication device or alatency parameter of the data stream, and to select an uncompressedcompression format and second spectrum, the router further configured totransmit or receive the data stream in the uncompressed compressionformat with the first spectrum and the second spectrum.

In Example 734, the subject matter of Example 733 can optionally includewherein the router is configured to transmit or receive the data streamin the uncompressed compression format with the first spectrum and thesecond spectrum by receiving the data stream in the uncompressedcompression format, splitting the data stream into a first part and asecond part, transmitting the first part via a first transceiver thatoperates on the first spectrum, and transmitting the second part via asecond transceiver that operates on the second spectrum.

In Example 735, the subject matter of Example 734 can optionally includewherein the router is configured to transmit or receive the data streamin the uncompressed compression format with the first spectrum and thesecond spectrum by receiving a first part of the data stream in theuncompressed compression format from a first transceiver that operateson the first spectrum, receiving a second part of the data stream in theuncompressed compression format from a second transceiver that operateson the second spectrum, and recombining the first part and the secondpart to obtain the data stream in the uncompressed compression format.

In Example 736, the subject matter of Example 734 or 735 can optionallyfurther include the first transceiver and the second transceiver.

In Example 737, the subject matter of Example 736 can optionally furtherinclude a first antenna and a second antenna, wherein the firsttransceiver is configured to wirelessly transmit and receive with thefirst antenna on the first spectrum and the second transceiver isconfigured to wirelessly transmit and receive with the second antenna onthe second spectrum.

In Example 738, the subject matter of any one of Examples 733 to 737 canoptionally further include a digital compression processor configured toreceive the data stream from a stream application before the routertransmits or receives the data stream in the first compression format,apply the first compression format to the data stream, and provide thedata stream in the first compression format to the router.

In Example 739, the subject matter of Example 738 can optionally furtherinclude the stream application, wherein the stream application isconfigured to generate the data stream in its initial format.

In Example 740, the subject matter of any one of Examples 733 to 737 canoptionally further include a digital compression processor configured toreceive the data stream from the router in the first compression formatafter the router receives the data stream in the first compressionformat, and to revert the first compression format.

In Example 741, the subject matter of Example 740 can optionally furtherinclude a stream application, wherein the digital compression processoris configured to provide the data stream to the stream application afterreverting the first compression format.

Example 742 is a terminal device including a first transceiverconfigured to transmit and receive on first spectrum, a secondtransceiver configured to transmit and receive on second spectrum, arouter configured to transmit or receive a data stream in a firstcompression format on the first spectrum via the first transceiver, anda controller configured to detect a triggering condition based on apower status of the communication device or a latency parameter of thedata stream, and to select a second compression format, the routerfurther configured to transmit or receive the data stream in the secondcompression format with the first spectrum and the second spectrum withthe first transceiver and the second transceiver.

Example 743 is a terminal device including a first transceiverconfigured to transmit and receive on first spectrum, a secondtransceiver configured to transmit and receive on second spectrum, arouter configured to transmit or receive a data stream in a firstcompression format on the first spectrum via the first transceiver, anda controller configured to detect a triggering condition based on apower status of the communication device or a latency parameter of thedata stream, and to select an uncompressed compression format, therouter further configured to transmit or receive the data stream in theuncompressed compression format with the first spectrum and the secondspectrum with the first transceiver and the second transceiver.

Example 744 is a method of transferring a data stream at a communicationdevice, the method including transmitting or receiving a data stream ina first compression format with first spectrum, detecting a triggeringcondition based on a power status of the communication device or alatency parameter of the data stream, and selecting a second compressionformat and second spectrum, and transmitting or receiving the datastream in the second compression format with the first spectrum and thesecond spectrum.

In Example 745, the subject matter of Example 744 can optionally includewherein the power status is a remaining battery power level of thecommunication device, and wherein detecting the triggering conditionincludes comparing the remaining battery power level to a battery powerlevel threshold and detecting the triggering condition if the remainingbattery power level is less than the battery power level threshold.

In Example 746, the subject matter of Example 744 can optionally includewherein the power status is a power-saving mode indicator that indicateswhether a power-saving mode of the communication device is enabled, andwherein detecting the triggering condition includes detecting thetriggering condition if the power-saving mode indicator indicates thatthe power-saving mode is enabled.

In Example 747, the subject matter of Example 744 can optionally includewherein the latency parameter of the data stream is a measured latencyof the data stream, and wherein detecting the triggering conditionincludes comparing the measured latency to a predefined latencythreshold and detecting the triggering condition if the measured latencyis greater than the predefined latency threshold.

In Example 748, the subject matter of any one of Examples 744 to 747 canoptionally further include applying the second compression format to thedata stream to obtain the data stream in the second compression format,wherein transmitting or receiving the data stream in the secondcompression format with the first spectrum and the second spectrumincludes splitting the data stream into a first part and a second part,transmitting the first part via a first transceiver that operates on thefirst spectrum, and transmitting the second part via a secondtransceiver that operates on the second spectrum.

In Example 749, the subject matter of Example 748 can optionally includewherein the second compression format is an uncompressed compressionformat, and wherein applying the second compression format to the datastream includes allowing the data stream to pass through withoutcompression processing.

In Example 750, the subject matter of Example 748 or 749 can optionallyfurther include generating the data stream at the stream application.

In Example 751, the subject matter of any one of Examples 744 to 747 canoptionally include wherein transmitting or receiving the data stream inthe second compression format with the first spectrum and the secondspectrum includes receiving a first part of the data stream in thesecond compression format from a first transceiver that operates on thefirst spectrum, receiving a second part of the data stream in the secondcompression format from a second transceiver that operates on the secondspectrum, and recombining the first part and the second part to obtainthe data stream in the second compression format.

In Example 752, the subject matter of Example 751 can optionally furtherinclude reverting the second compression format to obtain the datastream.

In Example 753, the subject matter of Example 752 can optionally include\wherein the second compression format is an uncompressed compressionformat, and wherein reverting the second compression format includesallowing the data stream to pass through without decompressionprocessing.

In Example 754, the subject matter of any one of Examples 744 to 753 canoptionally include wherein transfer of the data stream in the secondcompression format has a higher data rate demand than transfer of thedata stream in the first compression format, and wherein the controlleris configured to identify the second spectrum based on the higher datarate demand.

In Example 755, the subject matter of any one of Examples 744 to 754 canoptionally include wherein the second compression format is anuncompressed compression format.

In Example 756, the subject matter of any one of Examples 744 to 754 canoptionally include wherein the second compression format is a compressedcompression format.

In Example 757, the subject matter of any one of Examples 744 to 756 canoptionally include wherein the second compression format is more powerefficient than the first compression format.

In Example 758, the subject matter of any one of Examples 744 to 757 canoptionally include wherein the second compression format has lowerlatency than the first compression format.

In Example 759, the subject matter of any one of Examples 744 to 758 canoptionally include wherein the second compression format has lowercompression efficiency than the first compression format.

Example 760 is a method of transferring a data stream at a communicationdevice, the method including transmitting or receiving a data stream ina first compression format with first spectrum, detecting a triggeringcondition based on a power status of the communication device or alatency parameter of the data stream, and selecting an uncompressedcompression format and second spectrum, and transmitting or receivingthe data stream in the uncompressed compression format with the firstspectrum and the second spectrum.

In Example 761, the subject matter of Example 760 can optionally includewherein transmitting or receiving the data stream in the uncompressedcompression format with the first spectrum and the second spectrumincludes splitting the data stream into a first part and a second part,transmitting the first part via a first transceiver that operates on thefirst spectrum, and transmitting the second part via a secondtransceiver that operates on the second spectrum.

In Example 762, the subject matter of Example 761 can optionally furtherinclude generating the data stream at a stream application of thecommunication device before splitting the data stream.

In Example 763, the subject matter of Example 761 or 762 can optionallyfurther include applying the first compression format to the data streambefore transmitting or receiving the data stream in the firstcompression format.

In Example 764, the subject matter of Example 761 can optionally includewherein transmitting or receiving the data stream in the uncompressedcompression format with the first spectrum and the second spectrumincludes receiving a first part of the data stream in the uncompressedcompression format from a first transceiver that operates on the firstspectrum, receiving a second part of the data stream in the uncompressedcompression format from a second transceiver that operates on the secondspectrum, and recombining the first part and the second part to obtainthe data stream in the uncompressed compression format.

In Example 765, the subject matter of Example, can optionally includeincluding reverting the first compression format after receiving thedata stream in the first compression format.

Example 766 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 744 to765.

Example 767 is a device including one or more processors, and a memorystoring instructions that when executed by the one or more processorscause the one or more processors to perform the method of any one ofExamples 744 to 765.

Example 768 is a communication device including one or more processorsconfigured to transmit or receive a data stream in a first compressionformat with first spectrum, detect a triggering condition based on apower status of the communication device or a latency parameter of thedata stream, and select a second compression format and second spectrum,and transmit or receive the data stream in the second compression formatwith the first spectrum and the second spectrum.

Example 769 is a communication device including one or more processorsconfigured to transmit or receive a data stream in a first compressionformat with first spectrum, detect a triggering condition based on apower status of the communication device or a latency parameter of thedata stream, and select an uncompressed compression format and secondspectrum, and transmit or receive the data stream in the uncompressedcompression format with the first spectrum and the second spectrum.

Example 770 is a communication device including means for transmittingor receiving a data stream in a first compression format with firstspectrum, means for detecting a triggering condition based on a powerstatus of the communication device or a latency parameter of the datastream, and selecting a second compression format and second spectrum,and means for transmitting or receiving the data stream in the secondcompression format with the first spectrum and the second spectrum.

Example 771 is a communication device including means for transmittingor receiving a data stream in a first compression format with firstspectrum, means for detecting a triggering condition based on a powerstatus of the communication device or a latency parameter of the datastream, and selecting an uncompressed compression format and secondspectrum, and means for transmitting or receiving the data stream in theuncompressed compression format with the first spectrum and the secondspectrum.

Example 772 is a method of flying an aerial vehicle for station-keepingrelative to a target zone, the method including determining a targetzone based on one or more targets, determining a flight path for theaerial vehicle within the target zone, the flight path including a firstpath in which the aerial vehicle follows a same direction as a headwindhaving a first velocity and a second path in which the aerial vehiclemoves in a direction against a headwind having a second velocity lessthan the first velocity, and flying the aerial vehicle along the flightpath.

In Example 773, the subject matter of Example 772 can optionally includewherein the aerial vehicle includes an application system.

In Example 774, the subject matter of any one of Examples 772 or 773 canoptionally include wherein the one or more targets change location overtime.

In Example 775, the subject matter of any one of Examples 772-774 canoptionally further include operating the application system with the oneor more targets.

In Example 776, the subject matter of any one of Examples 772-775 canoptionally include wherein the target zone is based on a maximum rangeof the application system operating with the one or more targets.

In Example 777, the subject matter of any one of Examples 772-776 canoptionally include wherein the target zone further includes a targetlocation based on an optimal range of the application system operatingwith the one or more targets.

In Example 778, the subject matter of any one of Examples 772-777 canoptionally further include flying the aerial vehicle along the flightpath with a ground speed based on one-half the difference of the firstvelocity and the second velocity.

In Example 779, the subject matter of any one of Examples 772-778 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 780, the subject matter of any one of Examples 772-779 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 781, the subject matter of any one of Examples 772-780 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 782, the subject matter of any one of Examples 772-781 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

In Example 783, the subject matter of any one of Examples 772-782 canoptionally include wherein the application system includes a mobileaccess point.

In Example 784, the subject matter of any one of Examples 772-783 canoptionally include wherein the application system includes a sensingsystem.

Example 785 is a method of flying an aerial vehicle including a mobileaccess point along a flight path, the method including determining atarget zone based on one or more terminal devices that are configured tocommunicate with the mobile access point, determining a flight path forthe aerial vehicle within the target zone, the flight path including afirst path in which the aerial vehicle follows a same direction as aheadwind having a first velocity and a second path in which the aerialvehicle moves in a direction against a headwind having a second velocityless than the first velocity, and flying the aerial vehicle along theflight path.

In Example 786, the subject matter of Example 785 can optionally includewherein the target zone is based on a maximum communication range of themobile access point.

In Example 787, the subject matter of any one of Examples 785 or 786 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 788, the subject matter of any one of Examples 785-787 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter threshold for communications with the one or more terminaldevices.

In Example 789, the subject matter of any one of Examples 787 or 788 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 790, the subject matter of any one of Examples 787-789 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 791, the subject matter of any one of Examples 785-790 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 792, the subject matter of any one of Examples 785-791 canoptionally further include flying the aerial vehicle along the flightpath with a ground speed based on one-half the difference of the firstvelocity and the second velocity.

In Example 793, the subject matter of any one of Examples 785-792 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 794, the subject matter of any one of Examples 785-793 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 795, the subject matter of any one of Examples 785-794 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 796, the subject matter of any one of Examples 785-795,wherein a charging station for the aerial vehicle is located along theflight path.

In Example 797, the subject matter of any one of Examples 785-796 canoptionally further include communicating with the one or more terminaldevices in the target zone.

Example 798 is an aerial vehicle including an application systemincluding a mobile access point configured to communicate with one ormore terminal devices, a processor configured to determine a target zonebased on the one or more terminal devices, determine a flight path forthe aerial vehicle within the target zone, the flight path includingfirst path in which the aerial vehicle follows a same direction as aheadwind having a first velocity and a second path in which the aerialvehicle moves in a direction against a headwind having a second velocityless than the first velocity, and an aviation system configured to flythe aerial vehicle along the flight path.

In Example 799, the subject matter of Example 798 can optionally includewherein the target zone is based on a maximum communication range of themobile access point.

In Example 800, the subject matter of any one of Examples 798 or 799 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 801, the subject matter of any one of Examples 798-800 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter threshold for communications with the one or more terminaldevices.

In Example 802, the subject matter of any one of Examples 800 or 801 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 803, the subject matter of any one of Examples 800-802 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 804, the subject matter of any one of Examples 798-803 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 805, the subject matter of any one of Examples 798-804 canoptionally include wherein the aviation system is further configured tofly the aerial vehicle along the flight path with a ground speed basedon one-half the difference of the first velocity and the secondvelocity.

In Example 806, the subject matter of any one of Examples 798-805 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 807, the subject matter of any one of Examples 798-806 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 808, the subject matter of any one of Examples 798-807 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 809, the subject matter of any one of Examples 798-808 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

In Example 810, the subject matter of any one of Examples 798-809 canoptionally further include a flight structure configured to be extendedor retracted based on an airspeed of the aerial vehicle.

Example 811 is an aerial vehicle for station-keeping relative to atarget zone, the aerial vehicle including a means for determining atarget zone based on one or more targets, a means for determining aflight path for the aerial vehicle within the target zone, the flightpath including a first path in which the aerial vehicle follows a samedirection as a headwind having a first velocity and a second path inwhich the aerial vehicle moves in a direction against a headwind havinga second velocity less than the first velocity, and a means for flyingthe aerial vehicle along the flight path.

In Example 812, the subject matter of Example 811 can optionally furtherinclude a means for interacting with the one or more targets.

In Example 813, the subject matter of any one of Examples 811 or 812 canoptionally include wherein the one or more targets change location overtime.

In Example 814, the subject matter of any one of Examples 811-813 canoptionally include wherein the target zone is based on a maximum rangeof the application system operating with the one or more targets.

In Example 815, the subject matter of any one of Examples 811-814 canoptionally include wherein the target zone further includes a targetlocation based on an optimal range of the application system operatingwith the one or more targets.

In Example 816, the subject matter of any one of Examples 811-815 canoptionally further include a means for flying the aerial vehicle alongthe flight path with a ground speed based on one-half the difference ofthe first velocity and the second velocity.

In Example 817, the subject matter of any one of Examples 811-816 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 818, the subject matter of any one of Examples 811-817 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 819, the subject matter of any one of Examples 811-818 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 820, the subject matter of any one of Examples 811-819 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

Example 821 is an aerial vehicle including a communications means alonga flight path, the method including a means for determining a targetzone based on one or more terminal devices that are configured tocommunicate with the communications means, a means for determining aflight path for the aerial vehicle within the target zone, the flightpath including a first path in which the aerial vehicle follows a samedirection as a headwind having a first velocity and a second path inwhich the aerial vehicle moves in a direction against a headwind havinga second velocity less than the first velocity, and a means for flyingthe aerial vehicle along the flight path.

In Example 822, the subject matter of Example 821 can optionally includewherein the target zone is based on a maximum communication range of thecommunications means.

In Example 823, the subject matter of any one of Examples 821 or 822 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 824, the subject matter of any one of Examples 821-823 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter threshold for communications with the one or more terminaldevices.

In Example 825, the subject matter of any one of Examples 823 or 824 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 826, the subject matter of any one of Examples 823-825 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 827, the subject matter of any one of Examples 821-826 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 828, the subject matter of any one of Examples 821-827 canoptionally further include a means for flying the aerial vehicle alongthe flight path with a ground speed based on one-half the difference ofthe first velocity and the second velocity.

In Example 829, the subject matter of any one of Examples 821-828 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 830, the subject matter of any one of Examples 821-829 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 831, the subject matter of any one of Examples 821-830 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 832, the subject matter of any one of Examples 821-831 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

In Example 833, the subject matter of any one of Examples 821-832 canoptionally further include a means for communicating with the one ormore terminal devices in the target zone.

Example 834 is a method of controlling a flight formation of a pluralityof aerial vehicles each including an application system, aviationsystem, and a power source, the method including determining individualapplication system energy consumption requirements for the plurality ofaerial vehicles, determining individual aviation system energyconsumption requirements for the plurality of aerial vehicles,determining a flight formation for the plurality of aerial vehicles, theflight formation including an aerial vehicle with the lowest applicationsystem energy consumption requirement flying in a position of the flightformation requiring the highest aviation system energy consumptionrequirement, and arranging the plurality of aerial vehicles in theflight formation.

In Example 835, the subject matter of Example 834 can optionally includeincluding adjusting positions of the plurality of aerial vehicles withinthe flight formation based on changing individual application systemenergy consumption requirements of the plurality of aerial vehicles.

In Example 836, the subject matter of Example 834 can optionally includewherein the application system includes a mobile access point.

In Example 837, the subject matter of any one of Examples 834 or 835 canoptionally include wherein the application system includes a sensingsystem.

In Example 838, the subject matter of any one of Examples 834 or 835 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a line in a direction of flight.

In Example 839, the subject matter of any one of Examples 834 or 835 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a V-shape.

Example 840 is a means for controlling a flight formation of a pluralityof aerial vehicles each including an application system, aviationsystem, and a power source, the method including a means for determiningindividual application system energy consumption requirements for theplurality of aerial vehicles, a means for determining individualaviation system energy consumption requirements for the plurality ofaerial vehicles, a means for determining a flight formation for theplurality of aerial vehicles, the flight formation including an aerialvehicle with the lowest application system energy consumptionrequirement flying in a position of the flight formation requiring thehighest aviation system energy consumption requirement, and a means forarranging the plurality of aerial vehicles in the flight formation.

In Example 841, the subject matter of Example 840 can optionally includeincluding adjusting positions of the plurality of aerial vehicles withinthe flight formation based on changing individual application systemenergy consumption requirements of the plurality of aerial vehicles.

In Example 842, the subject matter of Example 840 can optionally includewherein the application system includes a mobile access point.

In Example 843, the subject matter of any one of Examples 840 or 841 canoptionally include wherein the application system includes a sensingsystem.

In Example 844, the subject matter of any one of Examples 840 or 842 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a line in a direction of flight.

In Example 845, the subject matter of any one of Examples 840 or 842 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a V-shape.

Example 846 is a flight formation controller for a plurality of aerialvehicles each including an application system, aviation system, and apower source, the flight formation controller including a receiverconfigured to receive individual application system energy consumptionrequirements for the plurality of aerial vehicles and individualaviation system energy consumption requirements for the plurality ofaerial vehicles, a processor configured to determine a flight formationfor the plurality of aerial vehicles, the flight formation including anaerial vehicle with the lowest application system energy consumptionrequirement flying in a position of the flight formation requiring thehighest aviation system energy consumption requirement, and atransmitter to send information indicating the flight formation to theplurality of aerial vehicles.

In Example 847, the subject matter of Example 846 can optionally includewherein the processor is further configured to adjust positions of theplurality of aerial vehicles within the flight formation based onchanging individual application system energy consumption requirementsof the plurality of aerial vehicles.

In Example 848, the subject matter of Example 846 can optionally includewherein the application system includes a mobile access point.

In Example 849, the subject matter of any one of Examples 846 or 847 canoptionally include wherein the application system includes a sensingsystem.

In Example 850, the subject matter of any one of Examples 846 or 847 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a line in a direction of flight.

In Example 851, the subject matter of any one of Examples 846 or 847 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a V-shape.

Example 852 is an aerial vehicle including an aviation system configuredto control flight of the aerial vehicle, an application system includingan application device, the application system configured to control theapplication device, a power source configured to provide energy for theaviation system and the application system, a transmitter to sendindividual application system energy consumption requirements for theaerial vehicle and individual aviation system energy consumptionrequirements for the aerial vehicle, a receiver configured to receiveinformation indicating a flight formation for a plurality of aerialvehicles that includes the aerial vehicle, with the flight formationincluding an aerial vehicle with the lowest application system energyconsumption requirement flying in a position of the flight formationrequiring the highest aviation system energy consumption requirement,and the aviation system further configured to control the aerial vehicleto take position in the flight formation based on the informationindicating the flight formation.

In Example 853, the subject matter of Example 852 can optionally includewherein the receiver is further configured to receive an indication toadjust position of the aerial vehicle within the flight formation basedon changing individual application system energy consumptionrequirements of the plurality of aerial vehicles.

In Example 854, the subject matter of Example 852 can optionally includewherein the application device includes a mobile access point.

In Example 855, the subject matter of any one of Examples 852 or 853 canoptionally include wherein the application device includes a sensingsystem.

In Example 856, the subject matter of any one of Examples 852 or 853 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a line in a direction of flight.

In Example 857, the subject matter of any one of Examples 852 or 853 canoptionally include wherein the flight formation includes the pluralityof aerial vehicles in a V-shape.

Example 858 is a method of flying an aerial vehicle including a mobileaccess point along a flight path, the method including configuring themobile access point as a relay for a network access node and tocommunicate with one or more terminal devices, handing overcommunication of the one or more terminal devices from the networkaccess node to the mobile access point, determining a target zone basedon the one or more terminal devices, determining a flight path for theaerial vehicle within the target zone, and flying the aerial vehiclealong the flight path.

In Example 859, the subject matter of Example 858 can optionally includewherein the aerial vehicle follows the one or more terminal deviceswithin the target zone to a coverage area of a further network accessnode.

In Example 860, the subject matter of any one of Examples 858-859 canoptionally further include flying the aerial vehicle back to the networkaccess node after escorting the one or more terminal devices to thecoverage area of the further network access node.

In Example 861, the subject matter of any one of Examples 858-860 canoptionally include wherein the one or more terminals travel along apredefined route.

In Example 862, the subject matter of Example 861 can optionally includewherein the predefined route is based on a terrestrial transportationroute.

In Example 863, the subject matter of any one of Examples 861 or 862 canoptionally include wherein the terrestrial transportation route is overland.

In Example 864, the subject matter of any one of Examples 861-863 canoptionally include wherein the terrestrial transportation route is overwater.

In Example 865, the subject matter of any one of Examples 861-864 canoptionally include wherein the predefined route is based on an aviationtransportation route.

In Example 866, the subject matter of any one of Examples 861-865 canoptionally include wherein the predefined route is based on anastronautic transportation route.

In Example 867, the subject matter of any one of Examples 858-866 canoptionally include wherein the target zone is based on a maximumcommunication range of the mobile access point.

In Example 868, the subject matter of any one of Examples 858-867 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 869, the subject matter of any one of Examples 858-868 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter for communications with the one or more terminal devices.

In Example 870, the subject matter of any one of Examples 868 or 869 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 871, the subject matter of any one of Examples 868-870 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 872, the subject matter of any one of Examples 858-871 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 873, the subject matter of any one of Examples 858-872 canoptionally further include flying the aerial vehicle along the flightpath with a ground speed based on one-half the difference of the firstvelocity and the second velocity.

In Example 874, the subject matter of any one of Examples 858-873 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 875, the subject matter of any one of Examples 858-874 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 876, the subject matter of any one of Examples 858-875 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 877, the subject matter of any one of Examples 858-876 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

In Example 878, the subject matter of any one of Examples 858-877 canoptionally further include communicating with the one or more terminaldevices in the target zone.

Example 879 is an aerial vehicle including a mobile access pointconfigured to fly along a flight path, the aerial vehicle including ameans for configuring the mobile access point as a relay for a networkaccess node and to communicate with one or more terminal devices, ameans for handing over communication of the one or more terminal devicesfrom the network access node to the mobile access point, a means fordetermining a target zone based on the one or more terminal devices, ameans for determining a flight path for the aerial vehicle within thetarget zone, and a means for flying the aerial vehicle along the flightpath.

In Example 880, the subject matter of Example 879 can optionally includewherein the aerial vehicle follows the one or more terminal deviceswithin the target zone to a communication area of a further networkaccess node.

In Example 881, the subject matter of any one of Examples 879-880 canoptionally further include flying the aerial vehicle back to the networkaccess node after escorting the one or more terminal devices to thecommunication area of the further network access node.

In Example 882, the subject matter of any one of Examples 879-881 canoptionally include wherein the one or more terminals travel along apredefined route.

In Example 883, the subject matter of Example 882 can optionally includewherein the predefined route is based on a terrestrial transportationroute.

In Example 884, the subject matter of any one of Examples 882 or 883 canoptionally include wherein the terrestrial transportation route is overland.

In Example 885, the subject matter of any one of Examples 882-884 canoptionally include wherein the terrestrial transportation route is overwater.

In Example 886, the subject matter of any one of Examples 882-885 canoptionally include wherein the predefined route is based on an aviationtransportation route.

In Example 887, the subject matter of any one of Examples 882-886 canoptionally include wherein the predefined route is based on anastronautic transportation route.

In Example 888, the subject matter of any one of Examples 879-887 canoptionally include wherein the target zone is based on a maximumcommunication range of the mobile access point.

In Example 889, the subject matter of any one of Examples 879-888 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 890, the subject matter of any one of Examples 879-889 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter threshold for communications with the one or more terminaldevices.

In Example 891, the subject matter of any one of Examples 889 or 890 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 892, the subject matter of any one of Examples 889-891 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 893, the subject matter of any one of Examples 879-892 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 894, the subject matter of any one of Examples 879-893 canoptionally further include a means for flying the aerial vehicle alongthe flight path with a ground speed based on one-half the difference ofthe first velocity and the second velocity.

In Example 895, the subject matter of any one of Examples 879-894 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 896, the subject matter of any one of Examples 879-895 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 897, the subject matter of any one of Examples 879-896 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 898, the subject matter of any one of Examples 879-897 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

Example 899 is an aerial vehicle including a mobile access pointconfigured as a relay for a network access node and configured tocommunicate with one or more terminal devices, a processor configured todetermine a target zone based on the one or more terminal devices anddetermine a flight path for the aerial vehicle within the target zone,and an aviation system configured to fly the aerial vehicle along theflight path.

In Example 900, the subject matter of Example 899 can optionally includewherein the target zone follows the one or more terminal devices to acommunication area of a further network access node.

In Example 901, the subject matter of any one of Examples 899-900 canoptionally include wherein the processor is further configured tocontrol the aviation system to fly the aerial vehicle back to thenetwork access node after escorting the one or more terminal devices tothe communication area of the further network access node.

In Example 902, the subject matter of any one of Examples 899-901 canoptionally include wherein the one or more terminals travel along apredefined route.

In Example 903, the subject matter of Example 902 can optionally includewherein the predefined route is based on a terrestrial transportationroute.

In Example 904, the subject matter of any one of Examples 902 or 903 canoptionally include wherein the terrestrial transportation route is overland.

In Example 905, the subject matter of any one of Examples 902-904 canoptionally include wherein the terrestrial transportation route is overwater.

In Example 906, the subject matter of any one of Examples 902-905 canoptionally include wherein the predefined route is based on an aviationtransportation route.

In Example 907, the subject matter of any one of Examples 902-906 canoptionally include wherein the predefined route is based on anastronautic transportation route.

In Example 908, the subject matter of any one of Examples 899-907 canoptionally include wherein the target zone is based on a maximumcommunication range of the mobile access point.

In Example 909, the subject matter of any one of Examples 899-908 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 910, the subject matter of any one of Examples 899-909 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter threshold for communications with the one or more terminaldevices.

In Example 911, the subject matter of any one of Examples 909 or 910 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 912, the subject matter of any one of Examples 909-911 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 913, the subject matter of any one of Examples 899-912 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 914, the subject matter of any one of Examples 899-913 canoptionally include wherein the processor is further configured tocontrol the aviation system to fly the aerial vehicle along the flightpath with a ground speed based on one-half the difference of the firstvelocity and the second velocity.

In Example 915, the subject matter of any one of Examples 899-914 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 916, the subject matter of any one of Examples 899-915 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 917, the subject matter of any one of Examples 899-916 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 918, the subject matter of any one of Examples 899-917 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

Example 919 is a network access node configured to communicate with oneor more terminals, the network access node including an aerial vehicle,the aerial vehicle including a mobile access point configured as a relayfor the network access node and configured to communicate with the oneor more terminal devices, a processor configured to determine a targetzone based on the one or more terminal devices and determine a flightpath for the aerial vehicle within the target zone, and an aviationsystem configured to fly the aerial vehicle along the flight path, thenetwork access node further including a transceiver configured tocommunicate with the one or more terminals, a network access nodeprocessor configured to hand over communication of the one or moreterminal devices to the aerial vehicle.

In Example 920, the subject matter of Example 919 can optionally includewherein the target zone follows the one or more terminal devices to acommunication area of a further network access node.

In Example 921, the subject matter of any one of Examples 919-920 canoptionally include wherein the processor is further configured tocontrol the aviation system to fly the aerial vehicle back to thenetwork access node after escorting the one or more terminal devices tothe communication area of the further network access node.

In Example 922, the subject matter of any one of Examples 919-921 canoptionally include wherein the one or more terminals travel along apredefined route.

In Example 923, the subject matter of Example 922 can optionally includewherein the predefined route is based on a terrestrial transportationroute.

In Example 924, the subject matter of any one of Examples 922 or 923 canoptionally include wherein the terrestrial transportation route is overland.

In Example 925, the subject matter of any one of Examples 922-924 canoptionally include wherein the terrestrial transportation route is overwater.

In Example 926, the subject matter of any one of Examples 922-925 canoptionally include wherein the predefined route is based on an aviationtransportation route.

In Example 927, the subject matter of any one of Examples 922-926 canoptionally include wherein the predefined route is based on anastronautic transportation route.

In Example 928, the subject matter of any one of Examples 919-927 canoptionally include wherein the target zone is based on a maximumcommunication range of the mobile access point.

In Example 929, the subject matter of any one of Examples 919-928 canoptionally include wherein the target zone is based on a communicationquality parameter for communications with the one or more terminaldevices.

In Example 930, the subject matter of any one of Examples 919-929 canoptionally include wherein the target zone further includes a targetlocation based on a predefined threshold of a communication qualityparameter threshold for communications with the one or more terminaldevices.

In Example 931, the subject matter of any one of Examples 929 or 930 canoptionally include wherein the communication quality parameter is basedon a signal strength indicator.

In Example 932, the subject matter of any one of Examples 929-931 canoptionally include wherein the communication quality parameter is basedon a signal quality indicator.

In Example 933, the subject matter of any one of Examples 919-932 canoptionally include wherein the one or more terminal devices changelocation over time.

In Example 934, the subject matter of any one of Examples 919-933 canoptionally include wherein the processor is further configured tocontrol the aviation system to fly the aerial vehicle along the flightpath with a ground speed based on one-half the difference of the firstvelocity and the second velocity.

In Example 935, the subject matter of any one of Examples 919-934 canoptionally include wherein the first path is at a first altitude and thesecond path is at a second altitude lower than the first altitude.

In Example 936, the subject matter of any one of Examples 919-935 canoptionally include wherein the flight path further includes an ascentpath to the first altitude and a descent path to the second altitude.

In Example 937, the subject matter of any one of Examples 919-936 canoptionally include wherein the first path and/or the second path has agreater horizontal distance than a vertical distance of the ascent pathand/or the descent path.

In Example 938, the subject matter of any one of Examples 919-937 canoptionally include wherein a charging station for the aerial vehicle islocated along the flight path.

Example 939 is an aerial vehicle including a rotatable structureincluding an airfoil, a generator coupled with the rotatable structure,a battery coupled with the generator, the rotatable structure configuredto generate electricity that charges the battery when air passing overthe airfoil causes the rotatable structure and the generator to rotate.

Example 940 is a method of charging an aerial vehicle including arotatable structure including an airfoil, a generator coupled with therotatable structure, a battery coupled with the generator, the rotatablestructure configured to generate electricity that charges the batterywhen air passing over the airfoil causes the rotatable structure and thegenerator to rotate, the method including determining a flight path forthe aerial vehicle including a descent, flying the aerial vehicle in thedescent along the flight path at a velocity that air passing over theairfoil turns the rotatable structure and the generator to generateelectricity, and storing the electricity in the battery.

Example 941 is an aerial vehicle including a rotatable structureincluding an airfoil, a generator coupled with the rotatable structure,a battery coupled with the generator, the rotatable structure configuredto generate electricity that charges the battery when air passing overthe airfoil causes the rotatable structure and the generator to rotate,the aerial vehicle including a means for determining a flight path forthe aerial vehicle including a descent, a means for flying the aerialvehicle in the descent along the flight path at a velocity that airpassing over the airfoil turns the rotatable structure and the generatorto generate electricity, and a means for storing the electricity in thebattery.

Example 942 is a method of charging an aerial vehicle including arotatable structure including an airfoil, a generator coupled with therotatable structure, a battery coupled with the generator, the rotatablestructure configured to generate electricity that charges the batterywhen air passing over the airfoil causes the rotatable structure and thegenerator to rotate, the method including fixing the aerial vehicle to astructure in a wind with air passing over the airfoil that turns therotatable structure and the generator to generate electricity, andstoring the electricity in the battery.

Example 943 is an aerial vehicle including a rotatable structureincluding an airfoil, a generator coupled with the rotatable structure,a battery coupled with the generator, the rotatable structure configuredto generate electricity that charges the battery when air passing overthe airfoil causes the rotatable structure and the generator to rotate,the aerial vehicle including a means for fixing the aerial vehicle to astructure in a wind with air passing over the airfoil that turns therotatable structure and the generator to generate electricity, and ameans for storing the electricity in the battery.

Example 944 is a method of charging an aerial vehicle including arotatable structure including an airfoil, a generator coupled with therotatable structure, a battery coupled with the generator, the rotatablestructure configured to generate electricity that charges the batterywhen air passing over the airfoil causes the rotatable structure and thegenerator to rotate, the method including fixing the aerial vehicle to afurther aerial vehicle, transporting the aerial vehicle with the furtheraerial vehicle with air passing over the airfoil that turns therotatable structure and the generator to generate electricity, andstoring the electricity in the battery.

Example 945 is an aerial vehicle including a rotatable structureincluding an airfoil, a generator coupled with the rotatable structure,a battery coupled with the generator, the rotatable structure configuredto generate electricity that charges the battery when air passing overthe airfoil causes the rotatable structure and the generator to rotate,the aerial vehicle including a means for fixing the aerial vehicle to afurther aerial vehicle, a means for transporting the aerial vehicle withthe further aerial vehicle with air passing over the airfoil that turnsthe rotatable structure and the generator to generate electricity, and ameans for storing the electricity in the battery.

Example 946 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of Examples 772 to797, 834 to 839, 858 to 878, 940, 942, or 944.

Example 947 is a device including one or more processors, and a memorystoring instructions that when executed by the one or more processorscause the one or more processors to perform the method of any one ofExamples 772 to 797, 834 to 839, 858 to 878, 940, 942, or 944.

In Example 948, a communication device, including a receiver configuredto receive a first signal, comprising a pilot symbol, from a secondcommunication device; a generator configured to generate a firsttransmission symbol, wherein the first transmission symbol istransmitted, via the transmitter, at the same time and frequency as thereceived pilot symbol; a channel estimator configured to perform achannel estimate based on the received pilot symbol; a link adapterconfigured to modify a first data based on the channel estimate; and atransmitter is configured to transmit the modified first data to thesecond communication device.

In Example 949, the subject matter of Example 948 may include whereinthe first transmission symbol is a transmission pilot symbol.

In Example 950, the subject matter of Example 948 may include whereinthe first transmission symbol is a data symbol.

In Example 951, the subject matter of Examples 948-950 may includewherein modifying the first data comprises pre-equalizing the firstdata.

In Example 952, the subject matter of Examples 948-951 may includewherein modifying the first data comprises pre-coding the first data.

In Example 953, the subject matter of Example 952 may include whereinpre-coding the first data comprises coding the first data according to amodulation and coding scheme (MCS) index.

In Example 954, the subject matter of Examples 948-953 may includewherein modifying the first data comprises selecting a sub-frequencycarrier band to transmit the pre-equalized first data.

In Example 955, the subject matter of Examples 948-954 may include thegenerator configured to generate the first transmission symbol to beorthogonal to the pilot symbol.

In Example 956, the subject matter of Examples 948-955 may include aninterference reducer configured to reduce an interference in thereceived pilot symbol resulting from the transmission of the firsttransmission symbol.

In Example 957, the subject matter of Example 956 may include whereinthe channel estimator is configured to perform the channel estimatebased on the received pilot symbol with the reduced interference.

In Example 958, a communication arrangement including a firstcommunication device configured to transmit a downlink signal comprisingone or more downlink pilot symbols; a second communication deviceconfigured to receive a first downlink pilot symbol of the one or moredownlink pilot symbols; transmit a first uplink symbol at the same timeand frequency as the first downlink pilot symbol; perform a channelestimation based on the received first downlink pilot symbol; modify adata based on the channel estimation; and transmit the modified data tothe first communication device.

In Example 959, the subject matter of Example 958 may include whereinthe first communication device is a small cell network access node.

In Example 960, the subject matter of Examples 958-959 may includewherein the second communication device is a user terminal device.

In Example 961, the subject matter of Examples 958-960 may includewherein the first uplink symbol is an uplink pilot symbol.

In Example 962, the subject matter of Examples 958-961 may includewherein the first uplink symbol is an uplink data symbol.

In Example 963, the subject matter of Examples 958-962 may includewherein modifying the data comprises pre-equalizing the first data.

In Example 964, the subject matter of Examples 958-963 may includewherein modifying the data comprises pre-coding the data.

In Example 965, the subject matter of Example 964 may include whereinthe pre-coding comprises coding the data according to a modulation andcoding scheme (MCS) index.

In Example 966, the subject matter of Examples 958-965 may includewherein modifying the data comprises selecting a sub-frequency carrierband to transmit the pre-equalized data.

In Example 967, the subject matter of Examples 958-966 may include thesecond communication device configured to transmit the first uplinksymbol so that it is orthogonal to the first downlink pilot symbol.

In Example 968, the subject matter of Examples 958-967 may include thesecond communication device further configured to reduce an interferencein the received first downlink pilot symbol resulting from thetransmission of the first uplink symbol.

In Example 969, the subject matter of Example 968 may include whereinthe channel estimation is performed based on the received first downlinkpilot symbol with the reduced interference.

In Example 970, a method for a first device to communicate with a seconddevice, the method including: generating a first transmission symbol atthe first device; receiving a first signal, comprising a pilot symbol,at the first device from the second device; transmitting the firsttransmission symbol at the same time and frequency as the received pilotsymbol to the second device; performing a channel estimate based on thereceived pilot symbol at the first device; modifying a first data basedon the channel estimate at the first device; and transmitting themodified first data to the second communication device.

In Example 971, the subject matter of Example 970 may include whereinthe first transmission symbol is a transmission pilot symbol.

In Example 972, the subject matter of Example 970 may include whereinthe first transmission symbol is a data symbol.

In Example 973, the subject matter of Examples 970-972 may includewherein modifying the first data comprises pre-equalizing the firstdata.

In Example 974, the subject matter of Examples 970-973 may includewherein modifying the first data comprises pre-coding the first data.

In Example 975, the subject matter of Example 974 may include whereinthe pre-coding comprises coding the first data according to a modulationand coding scheme (MCS) index.

In Example 976, the subject matter of Examples 970-975 may includewherein modifying the first data comprises selecting a sub-frequencycarrier band to transmit the pre-equalized first data.

In Example 977, the subject matter of Examples 970-976 may includegenerating the first transmission symbol to be orthogonal to the pilotsymbol.

In Example 978, the subject matter of Examples 970-977 may includereducing an interference in the received pilot symbol resulting from thetransmission of the first transmission symbol.

In Example 979, the subject matter of Example 978 may include whereinperforming the channel estimate is based on the received pilot symbolwith the reduced interference.

In Example 980, a communication device including a receiver configuredto one or more attach requests from one or more other communicationdevices; a processor configured to determine a criteria from the one ormore attach requests; and assign at least one of the one or more attachrequests to a respective cluster identification based on its determinedcriteria, wherein the cluster identification is allocated a respectiveset of resources from a total resource pool; a transmitter configured totransmit the cluster identification to at least one of the one or moreother communication devices.

In Example 981, the subject matter of Example 980 may include whereinthe communication device is a network access node.

In Example 982, the subject matter of Example 981 may include whereinthe network access node is a small cell network access node.

In Example 983, the subject matter of Examples 980-982 may includewherein the criteria comprises a power level.

In Example 984, the subject matter of Examples 980-983 may includewherein the criteria comprises a location.

In Example 985, the subject matter of Examples 980-984 may includewherein the respective cluster identification is generated in responseto the determined criteria.

In Example 986, the subject matter of Examples 980-984 may includewherein the respective cluster identification is retrieved from apreviously generated cluster identification.

In Example 987, a communication device including a processor configuredto generate an attach request to another communication device, whereinthe attach request comprises a device state information; transmit theattach request to the other communication device; receive a clusteridentification from the other communication device, wherein the clusteridentification is based on the device state information; and modify itstransmission and/or reception signal processing based on the clusteridentification.

In Example 988, the subject matter of Example 987 may include atransceiver.

In Example 989, the subject matter of Examples 987-988 may includewherein the device state information comprises a location information.

In Example 990, the subject matter of Examples 987-989 may includewherein the device state information comprises an information fordetermining a signal power.

In Example 991, the subject matter of Examples 987-990 may includewherein the signal processing comprises transmitting signals at aspecified time and/or frequency.

In Example 992, a method for wireless communication, the methodincluding transmitting an attach request from a first device to a seconddevice; determining a criteria for the attach request received at thesecond device; assigning the attach request to a respective clusteridentification based on the determined criteria, wherein the clusteridentification is allocated a respective set of resources from a totalresource pool; transmitting the cluster identification from the seconddevice to the first device; and modifying the first device'stransmission and/or reception signal processing based on the clusteridentification.

In Example 993, the subject matter of Example 992 may include whereinthe device state information comprises a location information.

In Example 994, the subject matter of Examples 992-993 may includewherein the device state information comprises an information fordetermining a signal power.

In Example 995, the subject matter of Examples 992-994 may includewherein the signal processing comprises transmitting signals at aspecified time and/or frequency.

In Example 996, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to Examples 970-979 or 992-995.

In Example 997, a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 970-979 or 992-995.

In Example 998, a communication device including means for receiving afirst signal, comprising a pilot symbol, from a second communicationdevice; means for transmitting; means for generating a firsttransmission symbol, wherein the first transmission symbol istransmitted, via the transmitting means, at the same time and frequencyas the received pilot symbol; means for performing channel estimatebased on the received pilot symbol; and means for modifying a first databased on the channel estimate; wherein the means for transmittingtransmits the modified first data to the second communication device.

In Example 999, a communication device including an antenna configuredto receive a plurality of signals, wherein each signal of the pluralityof signals is transmitted from a respective terminal device; and awaveform regulator configured to regulate the plurality of signals,wherein the regulation comprises harmonizing at least one offset amongthe plurality of signals; wherein the antenna is configured with a fixedantenna pattern for broadcasting the harmonized plurality of signalsover a target area.

In Example 1000, the subject matter of Example 999 may include whereinthe waveform regulator includes a time offset corrector configured tocorrect a time offset in the plurality of signals.

In Example 1001, the subject matter of Example 1000 may include whereinthe time offset corrector is configured to correlate each of theplurality of signals with a standard pattern.

In Example 1002, the subject matter of Example 1001 may include whereinthe standard pattern is a Primary Synchronization Signal (PSS) and/or aSecondary Synchronization Signal (SSS).

In Example 1003, the subject matter of Examples 999-1002 may includewherein the waveform regulator includes a frequency offset correctorconfigured to correct a frequency offset in the plurality of signals.

In Example 1004, the subject matter of Example 1003 may include whereinthe frequency offset corrector includes a frequency offset estimator.

In Example 1005, the subject matter of Examples 1003-1004 may includewherein the frequency offset corrector includes a frequency offsetcompensator.

In Example 1006, the subject matter of Examples 999-1005 may includewherein the waveform regulator includes a power offset correctorconfigured to correct a power offset in the plurality of signals.

In Example 1007, the subject matter of Example 1006 may include whereinthe power offset corrector includes a power level determiner configuredto determine a power level of each of the plurality of signals and apower equalizer configured to equalize the determined power levels.

In Example 1008, a communication arrangement including a plurality ofcommunication devices, wherein each communication device of theplurality of communication devices includes: an antenna configured toreceive a plurality of signals, wherein each signal of the plurality ofsignals is transmitted from a respective terminal device; a waveformregulator configured to regulate the plurality of signals, wherein theregulation comprises harmonizing at least one offset among the pluralityof signals; wherein the antenna is configured with a fixed antennapattern for broadcasting the harmonized plurality of signals over arespective target area.

In Example 1009, the subject matter of Example 1008 may include whereinthe respective target area of each communication device of the pluralityof communication devices covers a respective portion of an overall areaof interest.

In Example 1010, the subject matter of Examples 1008-1009 may includewherein the respective target areas of each communication devicecomprises at least one proximately located other communication device ofthe plurality of communication devices.

In Example 1011, the subject matter of Examples 1008-1010 may includewherein the waveform regulator comprises a time offset correctorconfigured to correct a time offset in the plurality of signals.

In Example 1012, the subject matter of Examples 1008-1011 may includewherein the time offset corrector is configured to correlate each of theplurality of signals with a standard pattern.

In Example 1013, the subject matter of Example 1012 may include whereinthe standard pattern is a Primary Synchronization Signal (PSS) and/or aSecondary Synchronization Signal (SSS).

In Example 1014, the subject matter of Examples 1008-1013 may includewherein the waveform regulator comprises a frequency offset correctorconfigured to correct a frequency offset in the plurality of signals.

In Example 1015, the subject matter of Example 1014 may include whereinthe frequency offset corrector comprises a frequency offset estimator.

In Example 1016, the subject matter of Examples 1014-1015 may includewherein the frequency offset corrector comprises a frequency offsetcompensator.

In Example 1017, the subject matter of Examples 1008-1016 may includewherein the waveform regulator comprises a power offset correctorconfigured to correct a power offset in the plurality of signals.

In Example 1018, the subject matter of Example 1017 may include whereinthe power offset corrector comprises a power level determiner configuredto determine a power level of each of the plurality of signals.

In Example 1019, a method for wireless communications, the methodincluding receiving plurality of signals, wherein each signal of theplurality of signals is transmitted from a respective terminal device;regulating the plurality of signals, wherein the regulation comprisesharmonizing at least one offset among the plurality of signals; andbroadcasting the regulated plurality of signals over a fixed targetarea.

In Example 1020, the subject matter of Example 1019 may includecorrecting a time offset in the plurality of signals.

In Example 1021, the subject matter of Example 1020 may include whereincorrecting the time offset comprises correlating each of the pluralityof signals with a standard pattern.

In Example 1022, the subject matter of Example 1021 may include whereinthe standard pattern is a Primary Synchronization Signal (PSS) and/or aSecondary Synchronization Signal (SSS).

In Example 1023, the subject matter of Examples 1019-1022 may includecorrecting a frequency offset in the plurality of signals.

In Example 1024, the subject matter of Example 1023 may include whereincorrecting the frequency offset comprises estimating the frequencyoffset among the plurality of signals.

In Example 1025, the subject matter of Examples 1023-1024 may includewherein correcting the frequency offset comprises compensating for theestimated frequency offset among the plurality of signals.

In Example 1026, the subject matter of Examples 1019-1025 may includecorrecting a power offset in the plurality of signals.

In Example 1027, the subject matter of Example 1026 may include whereincorrecting the power offset comprises determining a power level of eachof the plurality of signals and equalizing the power of the plurality ofsignals.

In Example 1028, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to Examples 1019-1027.

In Example 1029, a device including: a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1019-1027.

In Example 1030, a communication device including means for receiving aplurality of signals, wherein each signal of the plurality of signals istransmitted from a respective terminal device; means for regulating theplurality of signals, wherein the regulation comprises harmonizing atleast one offset among the plurality of signals; and means forbroadcasting the harmonized plurality of signals over a target area.

In Example 1031, a small cell communication arrangement including asmall cell network access node configured to provide access to anetwork; a plurality of remote radio heads (RRHs) in communication withthe small cell network access node, wherein each of the plurality ofRRHs is configured to serve as an interface for terminal devices in arespective target area of the small cell with the small cell networkaccess node.

In Example 1032, the subject matter of Example 1031 may include whereineach of the plurality of RRHs comprises an antenna configured to with afixed pattern to cover the RRHs respective target area.

In Example 1033, the subject matter of Examples 1031-1032 may includewherein the small cell network access node is configured as asynchronization source for the plurality of RRHs.

In Example 1034, the subject matter of Example 1031 may include whereinthe small cell network access node is configured to enable or disableone or more of the plurality of RRHs based on a detected activity in theone or more of the plurality of RRHs respective target area.

In Example 1035, a method for deploying a small cell communicationarrangement, the method including deploying a small cell network accessnode configured to provide access to a network; deploying a plurality ofremote radio heads (RRHs) in communication with the small cell networkaccess node, wherein each of the plurality of RRHs is configured toserve as an interface for terminal devices in a respective target areaof the small cell with the small cell network access node.

In Example 1036, a communication device for translating a first radioaccess technology (RAT) signal into a second RAT signal, thecommunication device including a receiver configured to receive a firstRAT signal, wherein the first RAT signal comprises unvarying symbols andunique symbols; a memory configured to store a look up table comprisingsecond RAT symbols corresponding to processed unvarying symbols of thefirst RAT; a processor configured to: retrieve at least one second RATsymbol from the memory; process the unique symbols of the first RATsignal in order to output corresponding symbols for the second RAT; andcombine the retrieved at least one second RAT symbol with the outputcorresponding symbols to generate the second RAT signal.

In Example 1037, the subject matter of Example 1036 may include atransmitter configured to transmit the second RAT signal.

In Example 1038, a method for translating a first radio accesstechnology (RAT) signal into a second RAT signal, the method including:receiving a first RAT signal, wherein the first RAT signal comprisesunvarying symbols and unique symbols; retrieving at least one second RATsymbol from the memory, wherein the memory is memory configured to storea look up table comprising second RAT symbols corresponding to processedunvarying symbols of the first RAT; processing the unique symbols of thefirst RAT signal in order to output corresponding symbols for the secondRAT; and combining the retrieved at least one second RAT symbol with theoutput corresponding symbols to generate the second RAT signal.

In Example 1039, the subject matter of Example 1038 may includetransmitting the second RAT signal.

In Example 1040, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to Examples 1038-1039.

In Example 1041, a device including: a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1038-1039.

In Example 1042, a communication device for translating a first radioaccess technology (RAT) signal into a second RAT signal, thecommunication device including: means for receiving a first RAT signal,wherein the first RAT signal comprises unvarying symbols and uniquesymbols; means for retrieving at least one second RAT symbol from thememory, wherein the memory is memory configured to store a look up tablecomprising second RAT symbols corresponding to processed unvaryingsymbols of the first RAT; means for processing the unique symbols of thefirst RAT signal in order to output corresponding symbols for the secondRAT; and means for combining the retrieved at least one second RATsymbol with the output corresponding symbols to generate the second RATsignal.

In Example 1043, a communication device including a processor configuredto trigger a transition to an RRC diagnostics mode, wherein the RRCdiagnostics mode comprises determining a status of one or more signalprocessing components of the communication device; determine if thestatus passes or fails an evaluation criterion; if the status fails theevaluation criterion, switch to an RRC calibration mode, wherein the RRCcalibration mode comprises communicating one or more calibration signalsbetween the communication device and a network access node.

In Example 1044, the subject matter of Example 1043 may include theprocessor further configured to measure a performance criteria of theone or more signal processing components based on the one or morecalibration signals.

In Example 1045, the subject matter of Example 1044 may include, theprocessor further configured to adjust one or more radio frequencyparameters of the one or more signal processing components based onmeasured performance criteria.

In Example 1046, the subject matter of Example 1045 may include theprocessor further configured to repeat the communicating of the one ormore calibration signals, the measuring of the performance criteria, andthe adjusting of the one or more radio frequency parameters until acondition is met.

In Example 1047, the subject matter of Example 1046 may include whereinthe condition is passing the evaluation criterion.

In Example 1048, the subject matter of Examples 1043-1047 may includewherein the communicating of the one or more calibration signalscomprises receiving, at the communication device, the calibrationsignals from the network access node.

In Example 1049, the subject matter of Example 1048 may include whereinthe one or more radio frequency parameters comprises radio receptionparameters.

In Example 1050, the subject matter of Example 1049 may include whereinthe radio reception parameters comprises at least one of: S-parametersfor an antenna tuner of the communication device, low oscillatorfrequency tuning, or analog gain values.

In Example 1051, the subject matter of Examples 1043-1047 may includewherein the communicating of the one or more calibration signalscomprises transmitting, from the communication device, the calibrationsignals to the network access node.

In Example 1052, the subject matter of Example 1051 may include whereinthe one or more radio frequency parameters comprises radio transmissionparameters.

In Example 1053, the subject matter of Examples 1051-1052 may includewherein the radio transmission parameters comprises at least one of: atransmit power offset, a transmit DC-DC path-delay, or a transmit poweramplifier distortion value.

In Example 1054, the subject matter of Examples 1043-1053 may includethe processor further configured to identify the one or more signalprocessing components wherein calibration of the one or more signalprocessing components fails the RRC calibration mode.

In Example 1055, the subject matter of Example 1054 may include theprocessor configured to replace the one or more signal processingcomponents.

In Example 1056, the subject matter of Examples 1043-1055 may includewherein the RRC diagnostics mode is triggered by the network accessnode.

In Example 1057, the subject matter of Examples 1043-1055 may includewherein the RRC diagnostics mode is triggered by the communicationdevice.

In Example 1058, the subject matter of Examples 1043-1057 may includewherein the RRC diagnostics mode is triggered by a timer.

In Example 1059, the subject matter of Examples 1043-1057 may includewherein the RRC diagnostics mode is triggered by an application layer.

In Example 1060, the subject matter of Examples 1043-1057 may includewherein the RRC diagnostics mode is triggered by a key performanceindicator (KPI).

In Example 1061, the subject matter of Example 1060 may include whereinthe KPI is at least one of: a frequency offset error estimated by thecommunication device or the network access node, an error vectormagnitude (EVM) measurement by a communication device receiver or anetwork access node receiver, or a Spur measurement in the communicationdevice downlink reception with the network access node.

In Example 1062, the subject matter of Examples 1043-1061 may includewherein the network access node is a small cell network access node.

In Example 1063, a method for calibrating a communication device, themethod including triggering a transition to an RRC diagnostics mode,wherein the RRC diagnostics mode comprises determining a status of oneor more signal processing components of the communication device;determining if the status passes or fails an evaluation criterion; ifthe status fails the evaluation criterion, switching to an RRCcalibration mode, wherein the RRC calibration mode comprisescommunicating one or more calibration signals between the communicationdevice and a network access node.

In Example 1064, the subject matter of Example 1063 may includemeasuring a performance criteria of the one or more signal processingcomponents based on the one or more calibration signals.

In Example 1065, the subject matter of Example 1064 may includeadjusting one or more radio frequency parameters of the one or moresignal processing components based on measured performance criteria.

In Example 1066, the subject matter of Example 1065 may includerepeating the communicating of the one or more calibration signals, themeasuring of the performance criteria, and the adjusting of the one ormore radio frequency parameters until a condition is met.

In Example 1067, the subject matter of Example 1066 may include whereinthe condition is passing the evaluation criterion.

In Example 1068, the subject matter of Examples 1063-1067 may includewherein the communicating of the one or more calibration signalscomprises receiving, at the communication device, the calibrationsignals from the network access node.

In Example 1069, the subject matter of Example 1068 may include whereinthe one or more radio frequency parameters comprises radio receptionparameters.

In Example 1070, the subject matter of Example 1069 may include whereinthe radio reception parameters comprises at least one of: S-parametersfor an antenna tuner of the communication device, low oscillatorfrequency tuning, or analog gain values.

In Example 1071, the subject matter of Examples 1063-1067 may includewherein the communicating of the one or more calibration signalscomprises transmitting, from the communication device, the calibrationsignals to the network access node.

In Example 1072, the subject matter of Example 1071 may include whereinthe one or more radio frequency parameters comprises radio transmissionparameters.

In Example 1073, the subject matter of Examples 1071-1072 may includewherein the radio transmission parameters comprises at least one of: atransmit power offset, a transmit DC-DC path-delay, or a transmit poweramplifier distortion value.

In Example 1074, the subject matter of Examples 1063-1073 may includeidentifying the one or more signal processing components whereincalibration of the one or more signal processing components fails theRRC calibration mode.

In Example 1075, the subject matter of Example 1074 may replacing theone or more signal processing components.

In Example 1076, the subject matter of Examples 1063-1075 may includewherein the RRC diagnostics mode is triggered by the network accessnode.

In Example 1077, the subject matter of Examples 1063-1075 may includewherein the RRC diagnostics mode is triggered by the communicationdevice.

In Example 1078, the subject matter of Examples 1063-1077 may includewherein the RRC diagnostics mode is triggered by a timer.

In Example 1079, the subject matter of Examples 1063-1077 may includewherein the RRC diagnostics mode is triggered by an application layer.

In Example 1080, the subject matter of Examples 1063-1077 may includewherein the RRC diagnostics mode is triggered by a key performanceindicator (KPI).

In Example 1081, the subject matter of Example 1080 may include whereinthe KPI is at least one of: a frequency offset error estimated by thecommunication device or the network access node, an error vectormagnitude (EVM) measurement by a communication device receiver or anetwork access node receiver, or a Spur measurement in the communicationdevice downlink reception with the network access node.

In Example 1082, the subject matter of Examples 1063-1081 may includewherein the network access node is a small cell network access node.

In Example 1083, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to Example 1063-1082.

In Example 1084, a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1063-1082.

In Example 1085, a communication device including means for triggering atransition to an RRC diagnostics mode, wherein the RRC diagnostics modecomprises determining a status of one or more signal processingcomponents of the communication device; means for determining if thestatus passes or fails an evaluation criterion; means for, if the statusfails the evaluation criterion, switching to an RRC calibration mode,wherein the RRC calibration mode comprises communicating one or morecalibration signals between the communication device and a networkaccess node.

In Example 1086, a communication device comprising a plurality radioaccess technology (RAT) links and a processor configured to: determine astatus of each of a plurality of RAT links of the communication device;rank the determined statuses of the plurality of RAT links; and select aRAT link to communicate a message based on the ranking

In Example 1087, a method for selecting a radio access technology (RAT)link from a plurality of RAT links of a communication device tocommunicate a message, the method including determining a status of eachof a plurality of RAT links of the communication device; ranking thedetermined statuses of the plurality of RAT links; and selecting the RATlink to communicate the message based on the ranking.

In Example 1088, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to Example 1087.

In Example 1089, a device including: a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of Example 1087.

In Example 1090, a communication device including means for determininga status of each of a plurality of RAT links of the communicationdevice; means for ranking the determined statuses of the plurality ofRAT links; and means for selecting the RAT link to communicate themessage based on the ranking.

In Example 1091, a communication device including an identifierconfigured to identify one or more regular users based on a usercriteria; a determiner configured to determine usage characteristics ofthe identified one or more regular users; and an adjuster configured toallocate resources of the communication device, provide a specificservice, or perform a link adaptation based on the usagecharacteristics.

In Example 1092, the subject matter of Example 1091 may include whereinthe user criteria comprises past user communication behavior with thecommunication device.

In Example 1093, the subject matter of Example 1092 may include whereinpast user behavior comprises timing information including at least oneof a start time, an end time, a frequency, or a duration which theidentified one or more users is in communication with the communicationdevice.

In Example 1094, the subject matter of Examples 1092-1093 may includewherein past user behavior comprises usage information comprising atleast one of latency requirements, data rate requirements, data traffictype requirements, or data type.

In Example 1095, the subject matter of Examples 1091-1094 may includethe identifier configured to group a plurality of identified users intoa user group.

In Example 1096, the subject matter of Example 1095 may include whereinthe adjuster configured to allocate resources of the communicationdevice, provide the specific service, or perform the link adaptation ina similar manner to all of the identified users in the user group.

In Example 1097, the subject matter of Examples 1091-1096 may includewherein the past user behavior comprises a location information.

In Example 1098, the subject matter of Example 1097 may include whereinthe adjuster is configured to perform the link adaptation based on thelocation information.

In Example 1099, the subject matter of Examples 1091-1098 may include auser monitor configured to monitor the identified user behavior andtrack any changes to the user criteria.

In Example 1100, the subject matter of Example 1099 may include whereinthe determiner is configured to determine updated usage characteristicsbased on tracked changes to the user criteria.

In Example 1101, the subject matter of Example 1100 may include whereinthe adjuster is configured to allocate resources of the communicationdevice, provide a specific service, or perform a link adaptation basedon the updated usage characteristics.

In Example 1102, the subject matter of Example 1091-1101 may includewherein the communication device is a small cell network access node.

In Example 1103, the subject matter of Example 1102 may include whereinthe small cell network access node is configured to store the usercriteria and usage characteristics in a database.

In Example 1104, the subject matter of Example 1103 may include whereinthe small cell network access node is configured to share the databasewith other network access nodes.

In Example 1105, the subject matter of Examples 1102-1104 may includewherein the small cell network access node comprises softwarereconfigurable resources.

In Example 1106, the subject matter of Example 1105 may include whereinthe software reconfigurable resources include field programmable gatearrays (FPGAs) and/or Digital Signal Processors (DSPs).

In Example 1107, the subject matter of Examples 1105-1106 may includewherein the adjuster is configured to program the softwarereconfigurable resources with executable code in order to allocateresources of the communication device, provide a specific service, orperform a link adaptation based on the usage characteristics.

In Example 1108, a method for a network access node to interact withusers, the method including: identifying one or more regular users basedon a user criteria; determining usage characteristics of the identifiedone or more regular users; and allocating resources of the networkaccess node, providing a specific service, or performing a linkadaptation based on the usage characteristics.

In Example 1109, the subject matter of Example 1108 may include whereinthe user criteria comprises past user communication behavior with thecommunication device.

In Example 1110, the subject matter of Example 1109 may include whereinpast user behavior comprises timing information including at least oneof a start time, an end time, a frequency, or a duration which theidentified one or more users is in communication with the communicationdevice.

In Example 1111, the subject matter of Examples 1109-1110 may includewherein past user behavior comprises usage information comprising atleast one of latency requirements, data rate requirements, data traffictype requirements, or data type.

In Example 1112, the subject matter of Examples 1108-1111 may includethe identifier configured to group a plurality of identified users intoa user group.

In Example 1113, the subject matter of Example 1112 may include whereinthe adjuster configured to allocate resources of the communicationdevice, provide the specific service, or perform the link adaptation ina similar manner to all of the identified users in the user group.

In Example 1114, the subject matter of Examples 1108-1113 may includewherein the past user behavior comprises a location information.

In Example 1115, the subject matter of Example 1114 may include whereinthe adjuster is configured to perform the link adaptation based on thelocation information.

In Example 1116, the subject matter of Examples 1108-1115 may includemonitoring the identified user behavior; and tracking any changes to theuser criteria.

In Example 1117, the subject matter of Example 1116 may includedetermining updated usage characteristics based on tracked changes tothe user criteria.

In Example 1118, the subject matter of Example 1117 may includeallocating resources of the communication device, providing a specificservice, or performing a link adaptation based on the updated usagecharacteristics.

In Example 1119, the subject matter of Examples 1108-1118 may includestoring the user criteria and usage characteristics in a database.

In Example 1120, the subject matter of Examples 1108-1119 may includewherein the network access node is a small cell network access node.

In Example 1121, the subject matter of Example 1120 may include whereinthe small cell network access node is configured to share the databasewith other network access nodes.

In Example 1122, the subject matter of Examples 1120-1121 may includewherein the small cell network access node comprises softwarereconfigurable resources.

In Example 1123, the subject matter of Example 1122 may include whereinthe software reconfigurable resources include field programmable gatearrays (FPGAs) and/or Digital Signal Processors (DSPs).

In Example 1124, the subject matter of Examples 1122-1123 may includeprogramming the software reconfigurable resources with executable codein order to allocate resources of the communication device, provide aspecific service, or perform a link adaptation based on the usagecharacteristics.

In Example 1125, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to any one of Examples 1108-1124.

In Example 1126, a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1108-1124.

In Example 1127, a communication device including means for identifyingone or more regular users based on a user criteria; means fordetermining usage characteristics of the identified one or more regularusers; and means for allocating resources of the network access node,providing a specific service, or performing a link adaptation based onthe usage characteristics.

In Example 1128, a network access node arrangement, including one ormore dedicated network access nodes, wherein each dedicated networkaccess node is configured to provide a specific optimized service; amaster node configured to: receive a service request from a terminaldevice; identify a respective dedicated network access node from the oneor more dedicated network access nodes configured to provide the requestservice; and redirect the terminal device to the respective dedicatednetwork access node.

In Example 1129, a method wireless communication in a network accessnode arrangement comprising a master network access node and one or morededicated network access nodes, the method including receiving, at themaster network access node, a service request from a terminal device;identifying, at the master network access node, a respective dedicatednetwork access from the one or more dedicated network access nodesconfigured to provide the request service; and redirecting the terminaldevice to the respective dedicated network access node.

In Example 1130, a network access node including: a receiver configuredto receive a plurality of download requests from one or more users; aprocessor configured to assign a priority to each of the downloadrequests; and sort the download requests based on their assignedpriorities; and a transmitter configured to transmit one or moredownload requests to the network based on the sort; wherein the receiveris configured to receive executable code from the network in response tothe one or more download requests, and wherein the processor isconfigured to download the executable code on a non-transitorycomputer-readable media of the network access node.

In Example 1131, the subject matter of Example 1130 may include theprocessor configured to retrieve the executable code and execute theexecutable code in response to a signal received from at least one ofthe one or more users.

In Example 1132, the subject matter of Examples 1130-1131 may includethe processor configured to relay a portion of the executable code tothe at least one of the one or more users.

In Example 1133, the subject matter of Example 1132 may include whereinthe executable code is executed jointly by the processor and the atleast one of the one or more users.

In Example 1134, the subject matter of Examples 1130-1133 may includewherein the network access node is a small cell network access node.

In Example 1135, the subject matter of Examples 1130-1134 may includewherein the executable code comprises code for an application.

In Example 1136, the subject matter of Examples 1130-1134 may includewherein the executable code comprises code for modifying a radiofrequency (RF) capability of the network access node.

In Example 1137, the subject matter of Examples 1130-1134 may includewherein the executable code comprises code for modifying a signalprocessing component of the network access node.

In Example 1138, the subject matter of Examples 1130-1134 may includewherein the executable code comprises code for new channel codingschemes or turbo coding.

In Example 1139, the subject matter of Examples 1130-1138 may includewherein the assignor is configured to assign download requestscomprising a safety information a higher priority than other downloadrequests.

In Example 1140, the subject matter of Examples 1130-1139 may includewherein the assignor is configured to assign a higher priority torepeated download requests.

In Example 1141, the subject matter of Examples 1130-1140 may includewherein the assignor is configured to assign the priority to each of thedownload requests based on a status of the user who submitted therequest.

In Example 1142, the subject matter of Example 1141 may include whereinthe status of the user is based at least in part on a frequency whichthe user access the network access node

In Example 1143, a method for configuring a network access node, themethod including receiving a plurality of download requests from one ormore users; assigning a priority to each of the download requests;sorting the download requests based on their assigned priorities;transmitting one or more download requests to the network based on thesort; receiving executable code from the network in response to the oneor more download requests; and downloading the executable code on anon-transitory computer-readable media of the network access node andreconfiguring the network access node based on the downloaded executablecode.

In Example 1144, the subject matter of Example 1143 may includeretrieving the executable code and executing the executable code inresponse to a signal received from at least one of the one or moreusers.

In Example 1145, the subject matter of Examples 1143-1144 may includerelaying a portion of the executable code to the at least one of the oneor more users.

In Example 1146, the subject matter of Example 1145 may include whereinthe executable code is executed jointly by the processor and the atleast one of the one or more users.

In Example 1147, the subject matter of Examples 1143-1146 may includewherein the network access node is a small cell network access node.

In Example 1148, the subject matter of Examples 1143-1147 may includewherein the executable code comprises code for an application.

In Example 1149, the subject matter of Examples 1143-1147 may includewherein the executable code comprises code for modifying a radiofrequency (RF) capability of the network access node.

In Example 1150, the subject matter of Examples 1143-1147 may includewherein the executable code comprises code for modifying a signalprocessing component of the network access node.

In Example 1151, the subject matter of Examples 1143-1147 may includewherein the executable code comprises code for new channel codingschemes or turbo coding.

In Example 1152, the subject matter of Examples 1143-1151 may includeassigning download requests comprising a safety information a higherpriority than other download requests.

In Example 1153, the subject matter of Examples 1143-1152 may includeassigning a higher priority to repeated download requests.

In Example 1154, the subject matter of Examples 1143-1153 may includeassigning the priority to each of the download requests based on astatus of the user who submitted the request.

In Example 1155, the subject matter of Example 1154 may include whereinthe status of the user is based at least in part on a frequency whichthe user access the network access node.

In Example 1156, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to any one of Examples 1143-1155.

In Example 1157, a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1143-1155.

In Example 1158, a network access node including means for receiving aplurality of download requests from one or more users; means forassigning a priority to each of the download requests; means for sortingthe download requests based on their assigned priorities; means fortransmitting one or more download requests to the network based on thesorting; means for receiving executable code from the network inresponse to the one or more download requests; and means for downloadingthe executable code on a non-transitory computer-readable media of thenetwork access node and reconfiguring the network access node based onthe downloaded executable code.

In Example 1159, a communication device including a node detectorconfigured to detect a plurality of nodes, wherein each node comprises acandidate for communications with the communication device; a processorconfigured to determine at least one of a mobility factor, coverage areafactor, or a processing capability factor, for each node of theplurality of nodes; sort the plurality of nodes into a hierarchy basedon its at least one determined factor; and communicate with at least afirst node of the plurality of nodes based on the hierarchy.

In Example 1160, the subject matter of Example 1159 may include whereinthe mobility factor is a node's movement.

In Example 1161, the subject matter of Example 1160 may include whereinthe node's movement is used to determine whether a respective node iseither a static node or a mobile node.

In Example 1162, the subject matter of Example 1161 may include whereinstatic nodes are fixed network infrastructure elements.

In Example 1163, the subject matter of Examples 1161-1162 may includewherein static nodes are further sorted into long range static nodes orshort range static nodes based on the coverage area factor.

In Example 1164, the subject matter of Example 1163 may include whereinthe coverage area factor comprises a node's communication range.

In Example 1165, the subject matter of Examples 1163-1164 may includewherein long range static nodes comprise macro cell network accessnodes.

In Example 1166, the subject matter of Examples 1163-1165 may includewherein short range static nodes comprise Road Side Units (RSUs) orfixed small cell network access nodes.

In Example 1167, the subject matter of Example 1161 may include whereinmobile nodes comprise vehicular communication devices.

In Example 1168, the subject matter of Example 1167 may include whereinthe mobility factor is used to determine whether a node has a similarmovement pattern or a different movement pattern to that of thecommunication device.

In Example 1169, the subject matter of Example 1168 may include whereinthe mobility factor comprises at least one of a velocity information,location information, or a Doppler Shift detection.

In Example 1170, the subject matter of Examples 1159-1169 may includewherein the hierarchy comprises a static node level and a mobile nodelevel.

In Example 1171, the subject matter of Example 1170 may include whereinthe static node level comprises long rage static nodes and short rangestatic nodes.

In Example 1172, the subject matter of Examples 1170-1171 may includewherein the mobile node level comprises mobile nodes with a similarmovement pattern to that of the communication device and mobile nodeswith a different movement pattern to that of the communication device.

In Example 1173, the subject matter of Examples 1159-1172 may includewherein the hierarchy is modified based on one or more additional nodesdetected by the node detector and each of the one or more additionalnodes corresponding mobility factor, coverage area factor, and/orprocessing capability factor.

In Example 1174, a method for a communication device to perform wirelesscommunications, the method including detecting a plurality of nodes;determining at least one of a mobility factor, coverage area factor, ora processing capability factor, for each node of the plurality of nodes;sorting the plurality of nodes into a hierarchy based on its at leastone determined factor; and communicating with at least a first node ofthe plurality of nodes based on the hierarchy.

In Example 1175, the subject matter of Example 1174 may include whereinthe mobility factor is a node's movement.

In Example 1176, the subject matter of Example 1175 may includeclassifying a respective node as a static node or a mobile node based onthe respective node's movement.

In Example 1177, the subject matter of Example 1176 may include whereinstatic nodes are fixed network infrastructure elements.

In Example 1178, the subject matter of Examples 1176-1177 may includesorting static nodes into long range static nodes or short range staticnodes based on the coverage area factor.

In Example 1179, the subject matter of Example 1178 may include whereinthe coverage area factor comprises a node's communication range.

In Example 1180, the subject matter of Examples 1178-1179 may includewherein long range static nodes comprise macro cell network accessnodes.

In Example 1181, the subject matter of Examples 1178-1180 may includewherein short range static nodes comprise Road Side Units (RSUs) orfixed small cell network access nodes.

In Example 1182, the subject matter of Example 1176 may include whereinmobile nodes comprise vehicular communication devices.

In Example 1183, the subject matter of Example 1182 may includedetermining whether a node has a similar movement pattern or a differentmovement pattern to that of the communication device based on the usingthe mobility factor.

In Example 1184, the subject matter of Example 1183 may include whereinthe mobility factor comprises at least one of a velocity information,location information, or a Doppler Shift detection.

In Example 1185, the subject matter of Example 1174-1184 may includewherein the hierarchy comprises a static node level and a mobile nodelevel.

In Example 1186, the subject matter of Example 1185 may include whereinthe static node level comprises long rage static nodes and short rangestatic nodes.

In Example 1187, the subject matter of Examples 1185-1186 may includewherein the mobile node level comprises mobile nodes with a similarmovement pattern to that of the communication device and mobile nodeswith a different movement pattern to that of the communication device.

In Example 1188, the subject matter of Examples 1174-1187 may includewherein the hierarchy is modified based on one or more additional nodesdetected by the node detector and each of the one or more additionalnodes corresponding mobility factor, coverage area factor, and/orprocessing capability factor.

In Example 1189, one or more non-transitory computer-readable mediastoring instructions thereon that, when executed by at least oneprocessor, direct the at least one processor to perform a methodaccording to any one of Examples 1174-1188.

In Example 1190, a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1174-1188.

In Example 1191, a communication device including means for detecting aplurality of nodes; means for determining at least one of a mobilityfactor, coverage area factor, or a processing capability factor, foreach node of the plurality of nodes; means for sorting the plurality ofnodes into a hierarchy based on its at least one determined factor; andmeans for communicating with at least a first node of the plurality ofnodes based on the hierarchy.

Example 1192 is a communication device connected to a radiocommunication network, the communication device including one or moreprocessors configured to apply one or more countermeasures based on anidentification to modify one or more components; and a transceiverconfigured to communicate based on the performed one or morecountermeasures.

In Example 1193, the subject matter of Example 1192 can optionallyinclude the one or more processors being further configured to determinean occurrence of one or more events.

In Example 1194, the subject matter of Example 1193 can optionallyinclude the one or more processors being further configured to identifythe one or more components based on the occurrence of one or moreevents.

Example 1195 is a communication device connected to a radiocommunication network, the communication device including one or moreprocessors configured to identify one or more components, and apply oneor more countermeasures based on the identification to modify the one ormore components; and a transceiver configured to communicate based onthe performed one or more countermeasures.

In Example 1196, the subject matter of Example 1195 can optionallyinclude the one or more processors being further configured to determinean occurrence of one or more events.

In Example 1197, the subject matter of Example 1196 can optionallyinclude the one or more processors being configured to identify the oneor more components based on the occurrence of the one or more events.

In Example 1198, the subject matter of any one of Examples 1192 to 1197can optionally include the communication device being implemented as aterminal device.

In Example 1199, the subject matter of any one of Examples 1192 to 1198can optionally include the communication device being implemented as avehicular communication device

In Example 1200, the subject matter of any one of Examples 1192 to 1197can optionally include the communication device being implemented as anetwork access node.

In Example 1201, the subject matter of any one of Examples 1192 to 1200can optionally include the one or more processors being furtherconfigured to initiate a diagnostic process in response to theoccurrence of the one or more events.

In Example 1202, the subject matter of Example 1201 can optionallyinclude the one or more processors being further configured to determineone or more initial conditions prior to initiating the diagnosticprocess.

In Example 1203, the subject matter of any one of Examples 1192 to 1202can optionally include the one or more countermeasures includesdisabling a component among the one or more components.

In Example 1204, the subject matter of Example 1203 can optionallyinclude the one or more countermeasures includes activating a redundancycomponent in place of the disabled component.

In Example 1205, the subject matter of any one of Examples 1192 to 1204can optionally include the one or more countermeasures includes anover-the-air update to modify the one or more components.

In Example 1206, the subject matter of any one of Examples 1192 to 1205can optionally include the one or more countermeasures includes acalibration process to modify the one or more components

In Example 1207, the subject matter of Example 1206 can optionallyinclude the calibration process includes updating one or more parametersto modify the one or more components.

In Example 1208, the subject matter of any one of Examples 1192 to 1207can optionally include the one or more processors being furtherconfigured to test a conformance of one or more components afterapplying the one or more countermeasures.

In Example 1209, the subject matter of any one of Examples 1206 to 1208can optionally include the diagnostic process being implemented as aself-diagnostic process and/or the calibration process being implementedas a self-calibration process.

In Example 1210, the subject matter of any one of Examples 1201 to 1209can optionally include the transceiver being further configured toprovide a result of the diagnostic process to the radio communicationnetwork.

In Example 1211, the subject matter of any one of Examples 1201 to 1210can optionally include the transceiver being further configured toprovide a result of the diagnostic process to a terminal device.

In Example 1212 is a method for communication over a radio communicationnetwork, the method including applying one or more countermeasures basedon an identification to modify one or more components; and communicatingbased on the performed one or more countermeasures.

In Example 1213, the subject matter of Example 1212, further includingdetermining an occurrence of one or more events.

In Example 1214, the subject matter of Example 1213 can optionallyinclude identifying the one or more components based on the occurrenceof one or more events.

In Example 1215 is a method for communicating over a radio communicationnetwork, the method including identifying one or more components;applying one or more countermeasures based on the identification tomodify the one or more components; and communicating based on theperformed one or more countermeasures.

In Example 1216, the subject matter of Example 1215 further includingdetermining an occurrence of one or more events.

In Example 1217, the subject matter of Example 1216 can optionallyinclude identifying one or more components by identifying the one ormore components based on the occurrence of the one or more events.

In Example 1218, the subject matter of any one of Examples 1212 to 1217can optionally include the one or more components being included in aterminal device.

In Example 1219, the subject matter of any one of Examples 1212 to 1218can optionally include the one or more components being included in avehicular communication device

In Example 1220, the subject matter of any one of Examples 1212 to 1217can optionally include the one or more components being identified by anetwork access node.

In Example 1221, the subject matter of any one of Examples 1212 to 1220,further including initiating a diagnostic process in response to theoccurrence of the one or more events.

In Example 1222, the subject matter of Example 1221, further includingdetermining one or more initial conditions prior to initiating thediagnostic process.

In Example 1223, the subject matter of any one of Examples 1212 to 1222can optionally include applying the one or more countermeasures includesdisabling a component among the one or more components.

In Example 1224, the subject matter of Example 1223 can optionallyinclude applying the one or more countermeasures includes activating aredundancy component in place of the disabled component.

In Example 1225, the subject matter of any one of Examples 1212 to 1224can optionally include applying the one or more countermeasures includesapplying an over-the-air update to modify the one or more components.

In Example 1226, the subject matter of any one of Examples 1212 to 1225can optionally include applying the one or more countermeasures includesperforming at least a portion of a calibration process to modify the oneor more components.

In Example 1227, the subject matter of Example 1226 can optionallyinclude performing at least a portion of the calibration processincludes updating one or more parameters to modify the one or morecomponents.

In Example 1228, the subject matter of any one of Examples 1212 to 66,further including testing a conformance of one or more components afterapplying the one or more countermeasures.

In Example 1229, the subject matter of any one of Examples 1226 to 1228can optionally include at least one of the diagnostic process beingimplemented as a self-diagnostic process and/or the calibration processbeing implemented as a self-calibration process.

In Example 1230, the subject matter of any one of Examples 1221 to 1229,further including providing a result of the diagnostic process to theradio communication network.

In Example 1231, the subject matter of any one of Examples 1221 to 1230,further including providing a result of the diagnostic process to aterminal device.

In Example 1232 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of: applying one or more countermeasures based on anidentification to modify one or more components; and communicating basedon the performed one or more countermeasures.

Example 1233 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of: identifying one or more components; applying oneor more countermeasures based on the identification to modify the one ormore components; and communicating based on the performed one or morecountermeasures.

Example 1234 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of any one of Examples 1212 to 1231.

Example 1235 is a non-transitory computer readable medium storinginstructions that when executed by processing circuitry of a computingdevice cause the computing device to perform the method of any one ofExamples 1212 to 1231.

Example 1236 is a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of: applying one or more countermeasures based on anidentification to modify one or more components; and communicating basedon the performed one or more countermeasures.

Example 1237 is a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of: identifying one or more components; applying oneor more countermeasures based on the identification to modify the one ormore components; and communicating based on the performed one or morecountermeasures.

Example 1238 is a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1212 to 1231.

Example 1239 is a communication device connected to a radiocommunication network, the communication device including means forapplying one or more countermeasures based on an identification tomodify one or more components; and means for communicating based on theperformed one or more countermeasures.

Example 1240 is a communication device connected to a radiocommunication network, the communication device including means foridentifying one or more components, and means for applying one or morecountermeasures based on the identification to modify the one or morecomponents; and means for communicating based on the performed one ormore countermeasures.

Example 1241 is a communication device connected to a radiocommunication network, the communication device including one or moreprocessors configured to perform at least a portion of a calibrationprocess based on an identification to modify one or more components; anda transceiver configured to communicate based on a result of thecalibration process.

In Example 1242, the subject matter of Example 1241 can optionallyinclude the one or more processors being further configured to selectbetween an unsupervised mode of operation and a supervised mode ofoperation based on whether a certificate is provided.

In Example 1243, the subject matter of Example 1242 can optionallyinclude the one or more processors being further configured to identifythe one or more components in accordance with the selected mode ofoperation.

Example 1244 is a communication device connected to a radiocommunication network, the communication device including one or moreprocessors configured to identify one or more components, and perform atleast a portion of a calibration process based on the identification tomodify the one or more components; and a transceiver configured tocommunicate based on a result of the calibration process.

In Example 1245, the subject matter of Example 1244 can optionallyinclude the one or more processors being further configured to selectbetween an unsupervised mode of operation and a supervised mode ofoperation based whether a certificate is provided.

In Example 1246, the subject matter of Example 1245 can optionallyinclude the one or more processors being configured to identify the oneor more components in accordance with the selected mode of operation.

In Example 1247, the subject matter of any one of Examples 1241 to 1246can optionally include the communication device being implemented as aterminal device.

In Example 1248, the subject matter of any one of Examples 1241 to 1247can optionally include the communication device being implemented as avehicular communication device

In Example 1249, the subject matter of any one of Examples 1241 to 1246can optionally include the communication device being implemented as anetwork access node.

In Example 1250, the subject matter of any one of Examples 1241 to 1249can optionally include the one or more processors being furtherconfigured to initiate a diagnostic process based on one or moretriggering conditions.

In Example 1251, the subject matter of Example 1250 can optionallyinclude the transceiver being further configured to receive a diagnosticnotification, and the received diagnostic notification indicates thecommunication device is to initiate to the diagnostic process.

In Example 1252, the subject matter of Example 1251 can optionallyinclude the received diagnostic notification being from a terminaldevice, and the one or more processors being further configured toperform at least a portion of the diagnostic process based on thereceived diagnostic notification.

In Example 1253, the subject matter of Example 1251 can optionallyinclude the received diagnostic notification being from the radiocommunication network, and the one or more processors being furtherconfigured to perform at least a portion of diagnostic process based onthe received diagnostic notification.

In Example 1254, the subject matter of any one of Examples 1250 to 1253can optionally include the transceiver being further configured totransmit one or more reference signals in accordance with the diagnosticprocess.

In Example 1255, the subject matter of any one of Examples 1250 to 1254can optionally include the transceiver being further configured toreceive one or more reference signals in accordance with the diagnosticprocess.

In Example 1256, the subject matter of any one of Examples 1250 to 1255can optionally include the transceiver being further configured toreceive a result of the diagnostic process based a comparison of the oneor more reference signals, and the result of the diagnostic processincludes the identification of the one or more components.

In Example 1257, the subject matter of any one of Examples 1250 to 1255can optionally include the one or more processors being furtherconfigured to determine a result of the diagnostic process based on acomparison of the one or more received reference signals; and the resultof the diagnostic process includes the identification of the one or morecomponents.

In Example 1258, the subject matter of any one of Examples 1250 to 1257can optionally include the diagnostic process being implemented as aself-diagnostic process.

In Example 1259, the subject matter of any one of Examples 1256 to 1258can optionally include the transceiver being further configured totransmit the result of the diagnostic process to the radio communicationnetwork.

In Example 1260, the subject matter of any one of Examples 1256 to 1259can optionally include the transceiver being further configured totransmit the result of the diagnostic process to the terminal device.

In Example 1261, the subject matter of any one of Examples 1256 to 1260can optionally include the one or more processors being configuredperform at least a portion of the calibration process in response todetermining the result of the diagnostic process.

In Example 1262, the subject matter of any one of Examples 1241 to 1261can optionally include the transceiver being configured to receive acalibration notification, and the received calibration notificationindicates the communication device is to initiate the calibrationprocess.

In Example 1263, the subject matter of Example 1262 can optionallyinclude the received calibration notification being from a terminaldevice, and the one or more processors being configured to perform atleast a portion of calibration process based on the received calibrationnotification.

In Example 1264, the subject matter of Example 1262 can optionallyinclude the received calibration notification being from the radiocommunication network, and the one or more processors being configuredto perform at least a portion of calibration process based on thereceived calibration notification.

In Example 1265, the subject matter of any one of Examples 1241 to 1264can optionally include the transceiver being further configured toreceive a result of the calibration process, and the result of thecalibration process includes an adjustment to one or more parametersassociated with the one or more components.

In Example 1266, the subject matter of any one of Examples 1241 to 1264can optionally include the one or more processors being furtherconfigured to determine a result of the calibration process, and theresult of the calibration process includes an adjustment to one or moreparameters associated with the one or more components.

In Example 1267, the subject matter of any one of Examples 1265 or 1266can optionally include the one or more processors being furtherconfigured to update the one or more parameters associated with the oneor more components based on the adjustment.

Example 1268 is a method for communicating over a radio communicationnetwork, the method including performing at least a portion of acalibration process based on an identification to modify one or morecomponents; and communicating based on a result of the calibrationprocess.

In Example 1269, the subject matter of Example 1268, further includingselecting between an unsupervised mode of operation and a supervisedmode of operation based on whether a certificate is provided.

In Example 1270, the subject matter of Example 1269, further includingidentifying one or more components in accordance with the selected modeof operation.

Example 1271 is a method for communicating over a radio communicationnetwork, the method including identifying one or more components;performing at least a portion of a calibration process based on theidentification to modify the one or more components; and communicatingbased on a result of the calibration process.

In Example 1272, the subject matter of Example 1271, further includingselecting between an unsupervised mode of operation and a supervisedmode of operation based whether a certificate is provided.

In Example 1273, the subject matter of Example 1272 can optionallyinclude identifying one or more components by identifying one or morecomponents in accordance with the selected mode of operation.

In Example 1274, the subject matter of any one of Examples 1268 to 1273,further including initiating a diagnostic process based on one or moretriggering conditions.

In Example 1275, the subject matter of Example 1274, further includingreceiving a diagnostic notification to initiate the diagnostic process.

In Example 1276, the subject matter of any one of Examples 1274 or 1275,further including performing at least a portion of the diagnosticprocess based on the received diagnostic notification, and canoptionally include the received diagnostic notification being from aterminal device.

In Example 1277, the subject matter of any one of Examples 1274 or 1275,further including performing at least a portion of the diagnosticprocess based on the received diagnostic notification, and canoptionally include the received diagnostic notification being from theradio communication network.

In Example 1278, the subject matter of any one of Examples 1274 to 1277,further including transmitting one or more reference signals inaccordance with the diagnostic process.

Example 1279, the subject matter of any one of Examples 1274 to 1278,further including receiving one or more reference signals in accordancewith the diagnostic process.

In Example 1280, the subject matter of any one of Examples 1274 to 1279,further including receiving a result of the diagnostic process based acomparison of the one or more reference signals, and can optionallyinclude the result of the diagnostic process includes the identificationof the one or more components.

In Example 1281, the subject matter of any one of Examples 1274 to 1279,further including comparing the one or more received reference signals;and determining a result of the diagnostic process based on a comparisonof the one or more received reference signals, and can optionallyinclude the result of the diagnostic process includes the identificationof the one or more components.

In Example 1282, the subject matter of any one of Examples 1274 to 1281can optionally include the diagnostic process being implemented as aself-diagnostic process.

In Example 1283, the subject matter of any one of Examples 1280 to 1282,further including providing the result of the diagnostic process to theradio communication network.

In Example 1284, the subject matter of any one of Examples 1280 to 1283,further including providing the result of the diagnostic process to theterminal device.

In Example 1285, the subject matter of any one of Examples 1280 to 1284can optionally include performing at least a portion of the calibrationprocess by performing at least a portion of the calibration process inresponse to determining the result of the diagnostic process.

In Example 1286, the subject matter of any one of Examples 1268 to 1285,further including receiving a calibration notification to initiate thecalibration process.

In Example 1287, the subject matter of Example 1286 can optionallyinclude the received calibration notification being from a terminaldevice, and performing at least a portion of the calibration process byperforming at least a portion of the calibration process based on thereceived calibration notification.

In Example 1288, the subject matter of Example 1286 can optionallyinclude the received calibration notification being from the radiocommunication network, and performing at least a portion of thecalibration process by performing at least a portion of the calibrationprocess based on the received calibration notification.

In Example 1289, the subject matter of any one of Examples 1280 to 1288,further including receiving the result of the calibration process, andcan optionally include the result of the calibration process includes anadjustment to one or more parameters associated with the one or morecomponents.

In Example 1290, the subject matter of any one of Examples 1280 to 1288,further including determining the result of the calibration process, andcan optionally include the result of the calibration process includes anadjustment to one or more parameters associated with the one or morecomponents.

In Example 1291, the subject matter of any one of Examples 1289 or 1290,further including updating the one or more parameters associated withthe one or more components based on the adjustment.

Example 1292 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of: performing at least a portion of a calibrationprocess based on an identification to modify one or more components; andcommunicating based on a result of the calibration process.

Example 1293 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of: identifying one or more components; andperforming at least a portion of a calibration process based on theidentification to modify the one or more components; and communicatingbased on a result of the calibration process.

Example 1294 is a non-transitory computer readable medium storinginstructions that when executed by a processor cause the processor toperform the method of any one of Examples 1268 to 1291.

Example 1295 is a non-transitory computer readable medium storinginstructions that when executed by processing circuitry of a computingdevice cause the computing device to perform the method of any one ofExamples 1268 to 1291.

Example 1296 is a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of: performing at least a portion of a calibrationprocess based on an identification to modify one or more components; andcommunicating based on a result of the calibration process.

Example 1297 is a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of: identifying one or more components; performing atleast a portion of a calibration process based on the identification tomodify the one or more components; and communicating based on a resultof the calibration process.

Example 1298 is a device including a processor; and a memory storinginstructions that when executed by the processor cause the processor toperform the method of any one of Examples 1268 to 1291.

Example 1299 is a communication device connected to a radiocommunication network, the communication device including means forperforming at least a portion of a calibration process based on anidentification to modify one or more components; and means forcommunicating based on a result of the calibration process.

Example 1300 is a communication device connected to a radiocommunication network, the communication device including means foridentifying one or more components, and means for performing at least aportion of a calibration process based on the identification to modifythe one or more components; and means for communicating based on aresult of the calibration process.

Example 1301 is a communication device comprising: a core signalingcontroller configured to attempt to initiate a first core networksignaling procedure through a first network access node, detect a radioaccess failure or disconnection for the first core network signalingprocedure, and start a timer for a second core network signalingprocedure; and a radio access processor configured to detect a secondnetwork access node, the core signaling controller further configured toattempt to initiate the second core network signaling procedure throughthe second network access node before the timer expires in response todetecting the second network access node.

In Example 1302, the subject matter of Example 1301 can optionallyinclude further comprising one or more antennas and a radio frequencytransceiver.

In Example 1303, the subject matter of Example 1301 can optionallyinclude configured as a baseband modem for a terminal device.

In Example 1304, the subject matter of any one of Examples 1301 to 1303can optionally include wherein the radio access processor comprises acell searcher configured to perform a cell search and to report thesecond network access node to the radio access processor.

In Example 1305, the subject matter of any one of Examples 1301 to 1304can optionally include wherein the core signaling controller isconfigured to perform non-Access Stratum (NAS) processing and signalingand the radio access processor is configured to perform Access Stratum(AS) processing and signaling.

In Example 1306, the subject matter of any one of Examples 1301 to 1305can optionally include wherein the timer has a standardized duration.

In Example 1307, the subject matter of any one of Examples 1301 to 1306can optionally include wherein the timer has a standardized timer thatdefines a duration of time to suspend core network signaling proceduresafter a radio access failure or disconnection.

In Example 1308, the subject matter of any one of Examples 1301 to 1307can optionally include wherein the core signaling controller isconfigured to determine whether the detected network access node is in afailed cell list of network access nodes that caused a radio accessfailure or disconnection for core network signaling procedures.

In Example 1309, the subject matter of Example 1308 can optionallyinclude where in the core signaling controller is further configured to,after detecting the radio access failure or disconnection for the firstcore network signaling procedure through the first network access node,adding identity information of the first network access node to thefailed cell list.

In Example 1310, the subject matter of any one of Examples 1301 to 1308can optionally include wherein the core signaling controller is furtherconfigured to increment a connection attempt counter after detecting theradio access failure or disconnection of the first core networksignaling procedure, and to determine that the connection attemptcounter is less than a threshold number of connection attempts beforeattempting to initiate the second core network signaling procedurethrough the second network access node.

In Example 1311, the subject matter of any one of Examples 1301 to 1310can optionally include wherein the core network signaling procedure is anon-Access Stratum (NAS) signaling procedure for Long Term Evolution(LTE).

Example 1312 is a communication device comprising: a core signalingcontroller configured to attempt to initiate a first core networksignaling procedure through a first network access node and to detect acore network failure for the first core network signaling procedure; anda radio access processor configured to detect a second network accessnode, the core signaling controller configured to determine whether thesecond network access node is in a same network tracking area as thefirst network access node and to attempt to initiate a second corenetwork signaling procedure through the second network access node inresponse to determining that the second network access node is not inthe same network tracking area.

In Example 1313, the subject matter of Example 1312 can optionallyinclude further comprising one or more antennas and a radio frequencytransceiver.

In Example 1314, the subject matter of Example 1312 can optionallyinclude configured as a baseband modem for a terminal device.

In Example 1315, the subject matter of any one of Examples 1312 to 1314can optionally include wherein the radio access processor comprises acell searcher configured to perform a cell search and to report thesecond network access node to the radio access processor.

In Example 1316, the subject matter of any one of Examples 1312 to 1315can optionally include wherein the core signaling controller isconfigured to determine not to attempt the second core network signalingprocedure through the second network access node if the second networkaccess node is in the same network tracking area.

In Example 1317, the subject matter of any one of Examples 1312 to 1316can optionally include wherein the core signaling controller isconfigured to add a network tracking area of the first network accessnode to a failed network tracking area list after detecting the corenetwork failure for the first core network signaling procedure.

In Example 1318, the subject matter of Example 1317 can optionallyinclude wherein the core signaling controller is configured to determinewhether a tracking area of the second network access node is in thefailed network tracking area list, and configured to attempt the secondcore network signaling procedure through the second network access nodein response to determining that the tracking area of the second networkaccess node is not in the failed network tracking area list.

In Example 1319, the subject matter of any one of Examples 1312 to 1318can optionally include wherein the first and second core networksignaling procedures are non-Access Stratum (NAS) signaling proceduresfor Long Term Evolution (LTE).

In Example 1320, the subject matter of any one of Examples 1312 to 1319can optionally include wherein the core signaling controller isconfigured to start a timer after the first core network signalingprocedure through the first network access node fails, and wherein thecore signaling controller is configured to attempt the second corenetwork signaling procedure through the second network access nodebefore the timer expires.

In Example 1321, the subject matter of Example 1320 can optionallyinclude wherein the timer has a standardized duration.

In Example 1322, the subject matter of Example 1320 can optionallyinclude wherein the timer is a standardized timer that defines aduration of time to suspend core network signaling procedures after atemporary core network failure.

Example 1323 is a communication device comprising: a core signalingcontroller configured to attempt to initiate a first core networksignaling procedure through a first network access node and to detect acore network failure for the first core network signaling procedure; anda radio access processor configured to identify one or more networkaccess nodes and to randomly select a second network access node fromthe one or more network access nodes, the core signaling controllerconfigured to attempt to initiate a second core network signalingprocedure through the second network access node.

In Example 1324, the subject matter of Example 1323 can optionallyinclude further comprising one or more antennas and a radio frequencytransceiver.

In Example 1325, the subject matter of Example 1324 can optionallyinclude configured as a baseband modem for a terminal device.

In Example 1326, the subject matter of any one of Examples 1323 to 1325can optionally include wherein the radio access processor comprises acell searcher configured to detect a plurality of available networkaccess nodes.

In Example 1327, the subject matter of Example 1326 can optionallyinclude wherein the radio access processor is configured to identify theone more network access nodes from the plurality of available networkaccess nodes based on which of the plurality of available network accessnodes satisfy a selection criteria.

In Example 1328, the subject matter of Example 1326 can optionallyinclude wherein the radio access processor is configured to identify theone more network access nodes from the plurality of available networkaccess nodes based on which of the plurality of available network accessnodes satisfy a selection criteria and are not on a potential fake celllist.

In Example 1329, the subject matter of Example 1328 can optionallyinclude wherein the core signaling controller is configured to add thefirst network access node to the potential fake cell list afterdetecting the core network failure of the first core network signalingprocedure through the first network access node

In Example 1330, the subject matter of any one of Examples 1323 to 1327can optionally include wherein the core signaling controller isconfigured to add the first network access node to a potential fake celllist after detecting the core network failure of the first core networksignaling procedure through the first network access node

In Example 1331, the subject matter of Example 1330 can optionallyinclude wherein core signaling controller is configured to determinethat the second network access node is not on the potential fake celllist before attempting the core second network signaling procedurethrough the second network access node.

In Example 1332, the subject matter of Example 1330 can optionallyinclude wherein the radio access processor is configured to identify theone or more network access nodes based on the potential fake cell list.

In Example 1333, the subject matter of any one of Examples 1323 to 1332can optionally include wherein the first and second core networksignaling procedures are non-Access Stratum (NAS) signaling proceduresfor Long Term Evolution (LTE).

In Example 1334, the subject matter of any one of Examples 1323 to 1333can optionally include wherein the core signaling controller isconfigured to start a timer after detecting the core network failure ofthe first core network signaling procedure, and wherein the coresignaling controller is configured to attempt the second core networksignaling procedure through the second network access node before thetimer expires.

In Example 1335, the subject matter of Example 1334 can optionallyinclude wherein the timer has a standardized duration.

In Example 1336, the subject matter of Example 1334 can optionallyinclude wherein the timer is a standardized timer that defines aduration of time to suspend core network signaling procedures after acore network failure.

Example 1337 is a communication device comprising: a primary radioaccess processor configured to perform a threshold number of failedconnection attempts for a first radio access technology; a primary coresignaling controller configured to start a timer for a subsequentconnection attempt for the first radio access technology, detect that asecond radio access technology is successfully registered, and toperform the subsequent connection attempt for the first radio accesstechnology before the timer expires if the second radio accesstechnology is successfully registered.

In Example 1338, the subject matter of Example 1337 can optionallyinclude further comprising one or more antennas and a radio frequencytransceiver.

In Example 1339, the subject matter of Example 1337 can optionallyinclude configured as a baseband modem for a terminal device.

In Example 1304, the subject matter of any one of Examples 1337 to 1339can optionally include further comprising: a legacy radio accessprocessor configured to perform radio access processing and signalingfor the second radio access technology; and a legacy core signalingcontroller configured to perform processing and signaling involved incommunications between the communication device and core network nodesfor the second radio access technology.

In Example 1341, the subject matter of Example 1340 can optionallyinclude wherein the legacy core signaling controller is configured toperform a registration procedure to register the communication devicewith a network of the second radio access technology.

In Example 1342, the subject matter of any one of Examples 1337 to 1341can optionally include wherein the primary radio access processor isconfigured to perform radio access processing and signaling for thefirst radio access technology, and wherein the primary core signalingcontroller is configured to perform processing and signaling involved incommunications between the communication device and core network nodesfor the first radio access technology.

In Example 1343, the subject matter of any one of Examples 1337 to 1342can optionally include wherein the primary core signaling controller isconfigured to perform the subsequent connection attempt for the firstradio access technology with a first network access node of the firstradio access technology, and to add a network tracking area of the firstnetwork access node to a failed network tracking area list if thesubsequent connection attempt fails.

In Example 1344, the subject matter of Example 1343 can optionallyinclude wherein the primary core signaling controller is configured to,if the subsequent connection attempt with the first network access nodefails, determine that a second network access node of the first radioaccess technology is in a network tracking area that is not in thefailed network tracking area list, and perform another connectionattempt for the first radio access technology with the second networkaccess node.

In Example 1345, the subject matter of any one of Examples 1337 to 1344can optionally include wherein the timer has a standardized duration.

In Example 1346, the subject matter of any one of Examples 1337 to 1344can optionally include wherein the timer is a standardized timer thatdefines a duration of time to suspend connection attempts after a radioaccess failure or disconnection of a connection attempt.

In Example 1347, the subject matter of any one of Examples 1337 to 1346can optionally include wherein the first radio access technology is LongTerm Evolution (LTE) and the second radio access technology is GlobalSystem for Mobile communications (GSM) or Universal MobileTelecommunications System (UMTS).

Example 1348 is a method of operating a communication device, the methodcomprising: attempting to initiate a first core network signalingprocedure through a first network access node; detecting a radio accessfailure or disconnection for the first core network signaling procedure;starting a timer for a second core network signaling procedure;detecting a second network access node; and attempting to initiate thesecond core network signaling procedure through the second networkaccess node before the timer expires in response to detecting the secondnetwork access node.

In Example 1349, the subject matter of Example 1348 can optionallyinclude wherein detecting the second network access node comprisesperforming a cell search to detect the second network access node.

In Example 1350, the subject matter of Example 1348 or 1349 canoptionally include wherein the timer has a standardized duration.

In Example 1351, the subject matter of any one of Examples 1348 to 1350can optionally include wherein the timer is a standardized timer thatdefines a duration of time to suspend core network signaling proceduresafter a radio access failure or disconnection.

In Example 1352, the subject matter of any one of Examples 1348 to 1351can optionally include further comprising: before attempting the secondcore network signaling procedure through the second network access node,determining whether the detected network access node is in a failed celllist of network access nodes that have been involved in a radio accessfailure or disconnection for core network signaling procedures.

In Example 1353, the subject matter of Example 1352 can optionallyinclude further comprising: after detecting the radio access failure ordisconnection for the first core network signaling procedure through thefirst network access node, adding identity information of the firstnetwork access node to the failed cell list.

In Example 1354, the subject matter of any one of Examples 1348 to 1353can optionally include further comprising: incrementing a connectionattempt counter after the first core network signaling procedure throughthe first network access node fails; and determining that the connectionattempt counter is less than a threshold number of connection attemptsbefore attempting the second core network signaling procedure throughthe second network access node.

In Example 1355, the subject matter of any one of Examples 1348 to 1354can optionally include wherein the core network signaling procedure is anon-Access Stratum (NAS) signaling procedure for Long Term Evolution(LTE).

Example 1356 is a method of operating a communication device, the methodcomprising: attempting to initiate a first core network signalingprocedure through a first network access node; detecting a core networkfailure for the first core network signaling procedure; detecting asecond network access node; determining whether the second networkaccess node is in a same network tracking area as the first networkaccess node; and attempting to initiate a second core network signalingprocedure through the second network access node in response todetermining that the second network access node is not in the samenetwork tracking area.

In Example 1357, the subject matter of Example 1356 can optionallyinclude wherein detecting the second network access node comprisesperforming a cell search to detect the second network access node.

In Example 1358, the subject matter of Example 1356 or 1357 canoptionally include further comprising determining not to attempt thesecond core network signaling procedure through the second networkaccess node if the second network access node is in the same networktracking area.

In Example 1359, the subject matter of any one of Examples 1356 to 1358can optionally include further comprising adding a network tracking areaof the first network access node to a failed network tracking area listafter the second core network signaling procedure through the firstnetwork access node fails.

In Example 1360, the subject matter of Example 1359 can optionallyinclude further comprising: determining whether a tracking area of thesecond network access node is in the failed network tracking area list;and attempting the second core network signaling procedure through thesecond network access node in response to determining that the trackingarea of the second network access node is not in the failed networktracking area list.

In Example 1361, the subject matter of any one of Examples 1356 to 1360can optionally include wherein the first and second core networksignaling procedures are non-Access Stratum (NAS) signaling proceduresfor Long Term Evolution (LTE).

In Example 1362, the subject matter of any one of Examples 1356 to 1361can optionally include further comprising: starting a timer after thefirst core network signaling procedure through the first network accessnode fails, wherein attempting to initiate the second core networksignaling procedure through the second network access node comprisesattempting to initiate the second core network signaling procedurethrough the second network access node before the timer expires.

In Example 1363, the subject matter of Example 1362 can optionallyinclude wherein the timer has a standardized duration.

In Example 1364, the subject matter of Example 1362 can optionallyinclude wherein the timer is a standardized timer that defines aduration of time to suspend core network signaling procedures after atemporary core network failure.

Example 1365 is a method of operating a communication device, the methodcomprising: attempting to initiate a first core network signalingprocedure through a first network access node; detecting a core networkfailure for the first core network signaling procedure; identifying oneor more network access nodes; randomly selecting a second network accessnode from the one or more network access nodes; and attempting toinitiate a second core network signaling procedure through the secondnetwork access node.

In Example 1366, the subject matter of Example 1365 can optionallyinclude further comprising detecting a plurality of available networkaccess nodes, wherein identifying the one or more network access nodescomprises identifying the one more network access nodes from theplurality of available network access nodes based on which of theplurality of available network access nodes satisfy a selectioncriteria.

In Example 1367, the subject matter of Example 1365 can optionallyinclude further comprising detecting a plurality of available networkaccess nodes, wherein identifying the one or more network access nodescomprises identifying the one more network access nodes from theplurality of available network access nodes based on which of theplurality of available network access nodes satisfy a selection criteriaand are not on a potential fake cell list.

In Example 1368, the subject matter of Example 1367 can optionallyinclude further comprising: after detecting the core network failure ofthe first core network signaling procedure through the first networkaccess node, adding the first network access node to the potential fakecell list.

In Example 1369, the subject matter of Example 1365 or 1366 canoptionally include further comprising: after detecting the core networkfailure of the first core network signaling procedure through the firstnetwork access node, adding the first network access node to a potentialfake cell list.

In Example 1370, the subject matter of Example 1369 can optionallyinclude further comprising determining that the second network accessnode is not on the potential fake cell list before attempting the secondcore network signaling procedure through the second network access node.

In Example 1371, the subject matter of Example 1369 can optionallyinclude wherein the radio access processor is configured to identify theone or more network access nodes based on the potential fake cell list.

In Example 1372, the subject matter of any one of Examples 1365 to 1371can optionally include wherein the core network signaling procedure is anon-Access Stratum (NAS) signaling procedure for Long Term Evolution(LTE).

In Example 1373, the subject matter of any one of Examples 1365 to 1372can optionally include further comprising: start a timer after detectingthe core network failure of the first core network signaling procedure,and wherein the core signaling controller is configured to attempt thesecond core network signaling procedure through the second networkaccess node before the timer expires.

In Example 1374, the subject matter of Example 1373 can optionallyinclude wherein the timer has a standardized duration.

In Example 1375, the subject matter of Example 1373 can optionallyinclude wherein the timer is a standardized timer that defines aduration of time to suspend core network signaling procedures after acore network failure.

Example 1376 is a method of operating a communication device, the methodcomprising: performing a threshold number of failed connection attemptsfor a first radio access technology; starting a timer for a subsequentconnection attempt for the first radio access technology; detecting thata second radio access technology is successfully registered; andperforming the subsequent connection attempt for the first radio accesstechnology before the timer expires if the second radio accesstechnology is successfully registered.

In Example 1377, the subject matter of Example 1376 can optionallyinclude further comprising performing a registration procedure for thesecond radio access technology to register the communication device witha network of the second radio access technology.

In Example 1378, the subject matter of Example 1376 or 1377 canoptionally include wherein performing the subsequent connection attemptfor the first radio access technology comprises performing thesubsequent connection attempt with a first network access node of thefirst radio access technology, the method further comprising adding anetwork tracking area of the first network access node to a failednetwork tracking area list if the subsequent connection attempt fails.

In Example 1379, the subject matter of Example 1378 can optionallyinclude further comprising: if the subsequent connection attempt withthe first network access node fails, determining that a second networkaccess node of the first radio access technology is in a networktracking area that is not in the failed network tracking area list; andperforming another connection attempt for the first radio accesstechnology with the second network access node.

In Example 1380, the subject matter of any one of Examples 1376 to 1379can optionally include where the timer has a standardized duration.

In Example 1381, the subject matter of any one of Examples 1376 to 1379can optionally include wherein the timer is a standardized timer thatdefines a duration of time to suspend connection attempts after a radioaccess failure or disconnection of a connection attempt.

In Example 1382, the subject matter of any one of Examples 1376 to 1381can optionally include wherein the first radio access technology is LongTerm Evolution (LTE) and the second radio access technology is GlobalSystem for Mobile communications (GSM) or Universal MobileTelecommunications System (UMTS).

Example 1383 is a non-transitory computer readable medium storinginstructions that when executed by one or more processors cause the oneor more processors to perform the method of any one of claims 1348 to1382.

Example 1384 is a device comprising: one or more processors; and amemory storing instructions that when executed by the one or moreprocessors cause the one or more processors to perform the method of anyone of claims 1348 to 1382.

Example 1385 is a communication device comprising: means for attemptingto initiate a first core network signaling procedure through a firstnetwork access node; means for detecting a radio access failure ordisconnection for the first core network signaling procedure; means forinitiating a time for a second core network signaling procedure; meansfor detecting a second network access node; and means for attempting toinitiate the second core network signaling procedure through the secondnetwork access node before the timer expires in response to detectingthe second network access node.

Example 1386 is a communication device comprising: means for attemptingto initiate a first core network signaling procedure through a firstnetwork access node; means for detecting a core network failure for thefirst core network signaling procedure; means for detecting a secondnetwork access node; means for determining whether the second networkaccess node is in a same network tracking area as the first networkaccess node; and means for attempting to initiate a second core networksignaling procedure through the second network access node in responseto determining that the second network access node is not in the samenetwork tracking area.

Example 1387 is a communication device comprising: means for attemptingto initiate a first core network signaling procedure through a firstnetwork access node; means for detecting a core network failure for thefirst core network signaling procedure; means for identifying one ormore network access nodes; means for randomly selecting a second networkaccess node from the one or more network access nodes; and means forattempting to initiate a second core network signaling procedure throughthe second network access node.

Example 1388 is a communication device comprising: means for performinga threshold number of failed connection attempts for a first radioaccess technology; means for starting a timer for a subsequentconnection attempt for the first radio access technology; means fordetecting that a second radio access technology is successfullyregistered; and means for performing the subsequent connection attemptfor the first radio access technology before the timer expires if thesecond radio access technology is successfully registered.

While the disclosure has been particularly shown and described withreference to specific aspects, it should be understood by those skilledin the art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the disclosure as definedby the appended claims. The scope of the disclosure is thus indicated bythe appended claims and all changes which come within the meaning andrange of equivalency of the claims are therefore intended to beembraced.

What is claimed is:
 1. A central trajectory controller comprising one ormore processors configured to: establish signaling connections with oneor more backhaul moving cells and establish signaling connections withone or more outer moving cells; obtain input data related to a radioenvironment of the one or more outer moving cells and the one or morebackhaul moving cells; determine, based on the input data, first coarsetrajectories for the one or more backhaul moving cells and second coarsetrajectories for the one or more outer moving cells; and generatetransmissions for the first coarse trajectories to the one or morebackhaul moving cells and for the second coarse trajectories to the oneor more outer moving cells.